Date: Thu, 30 Jun 2011 12:18:18 +0100 From: Julien Laffaye <jlaffaye@FreeBSD.org> To: Chris Rees <crees@freebsd.org> Cc: Jeremy Messenger <mezz.freebsd@gmail.com>, ports@freebsd.org, ohauer@freebsd.org Subject: Re: Call for testers -- CONF_FILES variable Message-ID: <4E0C5B7A.5060102@FreeBSD.org> In-Reply-To: <BANLkTi=nQByFgGNP--hkA4AF04Sw95s8jw@mail.gmail.com> References: <BANLkTikvMU2dK=aN=hFgxA8wfvUitmfbRA@mail.gmail.com> <BANLkTinBC184bwcQ1Sfyy9xsw9usqr3SJQ@mail.gmail.com> <BANLkTi=nQByFgGNP--hkA4AF04Sw95s8jw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/30/2011 08:22, Chris Rees wrote: >> >> 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 Yes, right now, pkgng uses the .pkgconf suffix to know that it is a configuration file. But now, we have a new format for the package manifest so _maybe_ (it has to be discussed with bapt) we can add an attribute to a file entry saying "I am a sample of a conf file". The hardest part for that would be to detect in the ports tree if we are using pkgng or the legacy pkg_install, and, depending on that, to generate the appropriate entry in the manifest / plist.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E0C5B7A.5060102>