Re: PKG_DBDIR under LOCALBASE (Was: ... default PKG_DBDIR)

[Steven Drake <sdrake%xnet.co.nz@localhost>]

On Tue, 1 Dec 2009, Joerg Sonnenberger wrote:
> On Tue, Dec 01, 2009 at 09:16:29AM +0000, David Brownlee wrote:
> > 3) Have default binaries that can use both locations, but option to
> > compile for only one
>
> I leave it for someone from DragonFly to speak up for that.
> Not sure how many other platforms have public repos to care about.

Correct me if I'm wrong, but only a few packages need to know the PKG_DBDIR
location, pkg_install and a dozen others under pkgtools!  So thats all the
packages that would have to be changed in a public repo.

On Tue, 1 Dec 2009, David Brownlee wrote:
> My preference would be for option 3. I would be inclined to go with:
> - If new location exists, use it
> - else if old location exists use it
> - else use new

Could work (its only 4 extra lines of code in pkg_install) but there's a 
problem, reinstalling the bootstrap kit could course both directorys to
exist, then what!
(Although it's probably a bad idea to reinstall the bootstrap kit anyway.)

On Tue, 1 Dec 2009 , David Brownlee wrote:
> I believe LOCALBASE/db

If it has to be a top level directory can it please start with at dot.
(eg "${LOCALBASE}/.pkgdb")

There is also a problem with moving PKG_DBDIR under LOCALBASE, it also moves
the PKG_REFCOUNT_DBDIR, which will create extra problems.


-- 
Steven
How should I know if it works?  That's what beta testers are for.  I
only coded it.
        -- Attributed to Linus Torvalds, somewhere in a posting