From owner-freebsd-ports@FreeBSD.ORG Mon Jan 7 06:18:56 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF14416A41B for ; Mon, 7 Jan 2008 06:18:56 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 61A9D13C465 for ; Mon, 7 Jan 2008 06:18:56 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 6492 invoked by uid 399); 7 Jan 2008 06:18:55 -0000 Received: from localhost (HELO ?192.168.0.4?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 7 Jan 2008 06:18:55 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <4781C447.2020808@FreeBSD.org> Date: Sun, 06 Jan 2008 22:18:47 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Naram Qashat References: <478068A6.7040408@cyberbotx.com> <47807231.6000202@FreeBSD.org> <478074A1.7020409@cyberbotx.com> In-Reply-To: <478074A1.7020409@cyberbotx.com> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: Ports that have multiple configuration files X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2008 06:18:56 -0000 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