On Tue, Feb 07, 2006 at 11:35:01AM -0800, Don Armstrong wrote: > On Tue, 07 Feb 2006, Frank K?ster wrote: > > Don Armstrong <[EMAIL PROTECTED]> wrote: > > > > > Right. The problem is that it's not always easy to know if the file > > > will no longer be read at all; you can't assume that the administrator > > > has left in place your default configuration system. > > > > Of course the maintainer should know their package. If the binary reads > > a configuration file in /usr/share/bla, and in the old version there was > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > This would be a problem. Not really, just nonideal; policy even covers it:
|10.7.2 Location | |Any configuration files created or used by your package must reside in |/etc. If there are several, consider creating a subdirectory of /etc |named after your package. | |If your package creates or uses configuration files outside of /etc, |and it is not feasible to modify the package to use /etc directly, put |the files in /etc and create symbolic links to those files from the |location that the package requires. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
