Date: Mon, 5 Jun 2000 13:46:59 +0300 (EEST) From: Adrian Penisoara <ady@warpnet.ro> To: Doug Barton <DougB@gorean.org> Cc: Satoshi Asami <asami@cs.berkeley.edu>, ports@freebsd.org Subject: Re: pine.conf Message-ID: <Pine.BSF.4.10.10006051324560.26875-100000@ady.warpnet.ro> In-Reply-To: <39395D01.9A4DC9A7@gorean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Doug answered just fine. Ady (@freebsd.ady.ro) On Sat, 3 Jun 2000, Doug Barton wrote: > Satoshi Asami wrote: > > > > Hi, > > > > mail/pine4/pkg/PLIST is creating pine.conf using the following two lines: > > > > @exec %D/bin/pine -P %D/etc/pine.conf -conf >%D/etc/pine.conf.tmp > > @exec /bin/mv %D/etc/pine.conf.tmp %D/etc/pine.conf > > > > I'm not sure what the -P option of pine does > > It specifies a specific conf file to use, instead of the default. > > > but this raises the following questions: > > > > (1) Does it preserve the user's existing pine.conf? (I assume it > > does, but just checking.) > > Yes. > > > (2) What would be an acceptable way of removing it on deinstallation? > > Is there a way to determine whether the user modified it to be > > something other than the "default" pine.conf? (If it is modified, > > it shouldn't be removed -- if it is not, then it can safely be > > removed, since a new installation will regenerate it properly.) > > '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. > > HTH, > > Doug > -- > "Live free or die" > - State motto of my ancestral homeland, New Hampshire > > Do YOU Yahoo!? > 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.10006051324560.26875-100000>