Date: Sun, 06 Jan 2008 22:18:47 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Naram Qashat <cyberbotx@cyberbotx.com> Cc: freebsd-ports@freebsd.org Subject: Re: Ports that have multiple configuration files Message-ID: <4781C447.2020808@FreeBSD.org> In-Reply-To: <478074A1.7020409@cyberbotx.com> References: <478068A6.7040408@cyberbotx.com> <47807231.6000202@FreeBSD.org> <478074A1.7020409@cyberbotx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Naram Qashat wrote:
> Doug Barton wrote:
>> Naram Qashat wrote:
>>> I had a question regarding what to do in a port Makefile when the port
>>> has multiple configuration files to install into PREFIX/etc. I read in
>>> the Porters Handbook about having to add entries into the Makefile and
>>> pkg-plist, but that seems to only be good for ports with a very small
>>> amount of configuration files. Is there an easy way to take a large
>>> collection of configuration files, change their extensions all to
>>> .conf.sample instead of .conf, set up all of them to be copied to .conf
>>> when they don't exist, and remove them all when they match the
>>> .conf.sample?
>>
>> Ummm ... use a loop? Take a look at mail/alpine for examples of using
>> shell commands vs. make commands for glob patterns.
>
> I can see how the loop would work within the Makefile. But I don't see
> how I would handle @unexec and @exec commands in pkg-plist for so many
> configuration files. I ask because there are 34 separate configuration
> files within the port I am trying to create.
Sorry, I still don't see the problem. If your concern is that it will
make the plist large, 34 of anything is still pretty tiny in terms of
lots of other things in ports.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4781C447.2020808>