On 2019/05/08 10:46, Tracey Emery wrote: > @sample won't overwrite existing configs in /etc. Also, the example is just an > example. People should read `man thingsd.conf` if they are confused to change > the NIC interface. I don't know, perhaps the sample is too exhaustive. Also, > the > interface can be completely removed to listen on all interfaces. So, I would > prefer the man approach for .conf information without any type of notice. > > Also, I believe without @sample, in deinstall, the notice to remove the config > gets lost. I'll be corrected if wrong.
That's all correct (plus pkg_delete -c uses @sample lines). > Thanks for your testing. > > On Wed, May 08, 2019 at 06:10:34PM +0200, Ampie Niemand wrote: > > Stephen / Tracey; Maybe it just needs a 'notice' after the port > > installation is done. > > > > I'm just wary of this instruction in the porters manual: btw, that's more of a guide than a manual, and it lags quite a lot behind common practice in the ports tree. > > Note: make sure host-dependent files go in /etc or /etc/<name>, but > > NEVER REPLACE OR MODIFY existing files in /etc. Best to have install > > place them in /usr/local/share/<name> and then copy to /etc or > > /etc/<name> only if the files do not exist. If the files exist, > > display a message that says such-and-such files need to be modified. > > This also guarantees that the files will be included in the package > > since everything under /usr/local is included in the PLIST. To handle > > the copying carefully, the @sample keyword is preferably used within > > the PLIST. After a package has been installed the contents of .. wording is a bit awkward but that is basically trying to point the reader at installing the files to PREFIX/share/whatever and using @sample to copy under SYSCONFDIR. > > pkg/MESSAGE will be displayed if it exists. (pkg/MESSAGE is meant just for very short messages of higher than usual importance, and some will even complain at that ;)
