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

[David Brownlee <abs%netbsd.org@localhost>]

2009/12/1 Julio Merino <jmmv%netbsd.org@localhost>:
> On Tue, Dec 1, 2009 at 4:16 AM, David Brownlee <abs%netbsd.org@localhost> 
> wrote:
>> I think we are safely post 2009Q3 :)
>>
>> I see three options:
>> 1) Change default PKG_DBDIR under LOCALBASE and have huge flag day fun
>> 2) Change default only for newer versions of each OS
>> 3) Have default binaries that can use both locations, but option to
>> compile for only one
>>
>> 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
>
> I think option 3 makes sense for the binaries.
>
> What is the proposed new location?

I believe LOCALBASE/db

Oh, I forgot option 4 which was to compile for new location and have
the binaries automatically copy any db from var to the new location if
the new location is empty. I'm listing it for completeness but would
prefer to avoid it.


2009/12/1 Joerg Sonnenberger <joerg%britannica.bec.de@localhost>:
> On Tue, Dec 01, 2009 at 09:16:29AM +0000, David Brownlee wrote:
>> I see three options:
>> 1) Change default PKG_DBDIR under LOCALBASE and have huge flag day fun
>
> Just change it in bootstrap. Existing installations continue to work.

Anyone re-installing bootstrap could break an existing system?

>> 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.

We certainly could make some systems build 'both location' binaries
and some 'new only', but my personal inclination would be to default
all to 'both location' now, and the in a year or so switch the default
to 'new only'.