On Sat, 2007-01-06 at 16:34 +0200, Shachar Shemesh wrote:
> Oded Arbel wrote:
> > Not having enough experience with Debian, and not having access to an
> > installation totting dpkg, why is -L not listing configuration files ?
> >
> Dpkg distinguishes between config files that always need to be modified
> and config files that arrive with a reasonable default. The way to
> handle the former is to dynamically generate them during the postinst
> script. Such files are not, strictly speaking, handled by the dpkg
> database, and will therefor not appear when you do dpkg -L.
>
> As Lior clearly demonstrated, files belonging to the later category WILL
> get listed when you do "dpkg -L".
I'm only familiar with RPMs notion of configuration files, in which
configuration files are also distributed but have a special behavior
where they are not overwritten when upgrading if they contain local
changes. I'm assuming that when you speak of configuration files with
reasonable defaults you speak of something similar to that.
But I'm not sure what you mean when you say "configuration files that
always need to be modified" - can you give some examples ?
xorg.conf ?
httpd.conf ?
aliases ?
syslog.conf ?
I find it interesting that one can somehow apply some rule to
distinguish between configuration files that "always" need to be changed
and configuration files that need to be changed only in some low
percentage of total installations.
--
Oded
::..
No violence, gentleman -- no violence, I beg of you! Consider the
furniture!
-- Sherlock Holmes
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
