Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Jun 2011 08:22:13 +0100
From:      Chris Rees <crees@freebsd.org>
To:        Jeremy Messenger <mezz.freebsd@gmail.com>
Cc:        ports@freebsd.org, ohauer@freebsd.org
Subject:   Re: Call for testers -- CONF_FILES variable
Message-ID:  <BANLkTi=nQByFgGNP--hkA4AF04Sw95s8jw@mail.gmail.com>
In-Reply-To: <BANLkTinBC184bwcQ1Sfyy9xsw9usqr3SJQ@mail.gmail.com>
References:  <BANLkTikvMU2dK=aN=hFgxA8wfvUitmfbRA@mail.gmail.com> <BANLkTinBC184bwcQ1Sfyy9xsw9usqr3SJQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 30 June 2011 01:35, Jeremy Messenger <mezz.freebsd@gmail.com> wrote:
> On Wed, Jun 29, 2011 at 3:24 PM, Chris Rees <crees@freebsd.org> wrote:
>> Dear all,
>>
>> I've rewritten the CONF_FILES handling after talking to bapt@, and
>> I've done away with the
>> colon-separated tuples -- they're overcomplicated.
>>
>> The result is something like MAN and PORTDOCS (indeed most of the code
>> is stolen from PORTDOCS).
>>
>> This means that shell globs, filenames and directories are specified
>> in CONF_FILES, but the sample file is installed in the Makefile as
>> .pkgconf.
>
> I like the rest, but I do not like the name of .pkgconf. I think, the
> 'pkgconf' is best define for something related with FreeBSD rather
> than third-party product. The .sample or .default is best name and
> less confuse for the users, because the word said it all what it is.

Thanks for the feedback.

I'm afraid any problems with the .pkgconf sample will have to be
discussed with the pkgng team and bapt@ -- wasn't my choice either.

Chris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTi=nQByFgGNP--hkA4AF04Sw95s8jw>