Date: Wed, 7 Jun 2000 13:28:30 +0300 (EEST) From: Adrian Penisoara <ady@warpnet.ro> To: Satoshi - Ports Wraith - Asami <asami@freebsd.org> Cc: Doug Barton <DougB@gorean.org>, ports@freebsd.org Subject: Re: pine.conf Message-ID: <Pine.BSF.4.10.10006071323340.97140-100000@ady.warpnet.ro> In-Reply-To: <vqcwvk2o5qi.fsf@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
On 6 Jun 2000, Satoshi - Ports Wraith - Asami wrote:
> * > > I'm not sure what the -P option of pine does
> * >
> * > It specifies a specific conf file to use, instead of the default.
>
> So this is a way to merge the user's changes (if any are in
> ${PREFIX}/etc/pine.conf) into the new pine's configuration, correct?
Exactly !
>
> * > 'pine -conf' will generate a default file for that version of pine on
> * > stdout. You could diff the installed version against that to detect
> * > changes.
>
> Ok. So will something like the following be acceptable? (I've just
> verified on bento that it indeed erases pine.conf.)
Seems OK, though I would be thinking about just printing a message
letting him know hat he may remove the file if he wants...
BTW, shouldn't we use a temporary path instead of the local tree ?
>
> Satoshi
> -------
> Index: pkg/PLIST
> ===================================================================
> RCS file: /home/ncvs/ports/mail/pine4/pkg/PLIST,v
> retrieving revision 1.13
> diff -u -r1.13 PLIST
> --- pkg/PLIST 1998/10/05 04:23:19 1.13
> +++ pkg/PLIST 2000/06/06 21:17:24
> @@ -1,3 +1,6 @@
> +@unexec %D/bin/pine -conf >%D/etc/pine.conf.tmp
> +@unexec if cmp -s %D/etc/pine.conf %D/etc/pine.conf.tmp; then rm -f %D/etc/pine.conf; fi
> +@unexec rm -f %D/etc/pine.conf.tmp
> bin/pico
> bin/pilot
> bin/pine
>
Ady (@warpnet.ro)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10006071323340.97140-100000>