Re: Moving mk.conf (Was: Making it easier to get and use pkgsrc)

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

Hijacking this across into the sub thread with my updated proposal.

2010/12/12 Aleksej Saushev <asau%inbox.ru@localhost>:
> David Brownlee <abs%netbsd.org@localhost> writes:
>
>> On 11 December 2010 23:59, David Holland 
>> <dholland-pkgtech%netbsd.org@localhost> wrote:
>>> On Sat, Dec 11, 2010 at 08:14:26PM +0000, David Brownlee wrote:
>>>  > - Switch from mk.conf to pkgsrc.conf
>>
>> A file under PKGSRCDIR would make me happy - I'm less concerned about the 
>> name
>
> I don't like it under PKGSRCDIR, it doesn't belong there.
> I can (and I do) have several pkgsrc trees in the same file names space
> operating fine with the same LOCALBASE using the same mk.conf.
> mk.conf belongs to deployment not the pkgsrc tree.
>
> I don't think that $(TOP)/mk.conf is good idea either.
>
> BTW, same should apply to pkgchk.conf, perhaps I should file PR on that.
> It is annoying that pkg_chk defaults to configuration and cache/index files
> in PKGSRCDIR.

I think we have conflicting requirements here - (as I understand it) you would
want any "pkgchk.conf" or similar to be shared across pkgsrc trees, as you
would want for any pkg_chk.conf or similar files, while I want them to be
pkgsrc tree specific. I specifically don't want to go messing around in mk.conf
when I switch to a different pkgsrc tree.

I'm assuming if they lived under PREFIX that would be no better for you?

What do you think about an environment variable which sets the basedir that
contains the config files (pkg_chk.conf, "pkgsrc.conf", and anything else
similar), though it may just be enough to specify it for "pkgsrc.conf" and
rely on values being set in there to affect everything else.