On Sat, 17 Mar 2001, phil@bolthole.com wrote: > On Sat, Mar 17, 2001 at 07:42:57AM -0300, Henrique M Holschuh wrote: > > On Sat, 17 Mar 2001, Colin Watson wrote: > > > >The irony is: For my particular program, the standard "app-defaults" file > > > >SHOULD NOT BE CONSIDERED A "CONF-FILE"! > > > > Then it doesn't belong in /etc. It is that simple. > > I'm following the X conventions. It's an app-defaults file, so I'm using > InstallAppDefaults() > It's the one that's putting it in /etc We have a failure of communication here. If it is in /etc (AND included in the package), it must be a conffile so that the local admin can change the site-wide defaults and not have it overwriten by dpkg. If it is automatically generated at every upgrade, don't include it in the .deb (at least not in /etc). If, on the other hand, the app-defaults file won't work as shipped inside the package (i.e.: it REQUIRES customization to even behave in a sensible way), it belongs in /usr/share or /usr/lib (lib is probably best if you use that file as the template input for a configure helper). Who cares where Imake wants to put the file? Overriding wherever the upstream Imake/Makefile/install script wants to write files is one of the most common changes a developer needs to do, IMHO. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Attachment:
pgpkYqqHPkpU4.pgp
Description: PGP signature