Lars Wirzenius [EMAIL PROTECTED] wrote:
Third scenario:
[snip]
This time the differences between the currently installed and
the new app-defaults file are huge. The output of `diff' is not
easy to understand, and the admin makes a mistake and assumes
that nothing important has changed, just
Christian Schwarz:
My suggestion of tagging the files as conffiles was thought as a solution
to your problem, if the files change.
The problem scenario:
Version 1.0 installs an app-defaults file. It defines
resource ``*Background: black''.
Admin installs
Christian Schwarz [EMAIL PROTECTED] writes:
My suggestion of tagging the files as conffiles was thought as a solution
to your problem, if the files change.
That's the problem, though---it's not a solution at all. Consider if
the application introduces a new resource, without which the
Hi!
Ok, you (Michael) made me change my standpoint. It's propably better to
consider app-defaults as part of the code and then it's ok if it stays
under /usr.
BTW, I just did a `grep app-defaults *.conffiles' in /var/lib/dpkg/info
and discovered, that there are a few packages specifying the
Michael Alan Dorman [EMAIL PROTECTED] writes:
I feel like a broken record, here, but would people involved in this
discussion please look at /usr/doc/X11/debian.README? Otherwise
you're wasting both your own and others' time.
For instance, it mentions the solution to the above mentioned
Yves Arrouye ([EMAIL PROTECTED]) wrote on 17 September 1996 00:10:
That wouldn't resolve Michael's problem: assume I change my
app-defaults file for SomeApp, just to adjust colors to my tastes.
Then comes a new release of SomeApp, with new features controlled by X
resources that are in the
Michael Alan Dorman:
I feel like a broken record, here, but would people involved in this
discussion please look at /usr/doc/X11/debian.README?
I did that. I didn't notice that paragraph, probably because it
comes under the heading of ``xdm-start-server''. The visual clues
given by the
Christian Schwarz [EMAIL PROTECTED] writes:
Well, couldn't the files in app-defaults be marked as config files
(DEBIAN/conffiles) in the packages?
Only if you want Ian Jackson to post a bug report against your
package---conffiles do not belong in /usr.
Please look at /usr/doc/X11/debian.README
If you disagree with this, as many seem to, please propose a solution
whereby package maintainers can easily make sure that app-defaults
files are updated to reflect any changes introduced in the upstream
app-defaults file.
Well, couldn't the files in app-defaults be marked as config
On Sep 16, 8:48pm, Christian Schwarz wrote:
} Subject: Re: Shouldn't go app-defaults in /etc/X11?
}
} Michael Alan Dorman [EMAIL PROTECTED] writes:
} If you disagree with this, as many seem to, please propose a solution
} whereby package maintainers can easily make sure that app-defaults
Brian C. White:
Personally, since these are _defaults_ that are intended to be overridden
by user configuration, I think they are fine where they are. These
programs are not system utilities that need to be configured. These
are just defaults and there are documented ways for a user to
Lars Wirzenius [EMAIL PROTECTED] writes:
However, a sysadmin might want to have a way to make a global override.
For example, to configure Mosaic to use a proxy. Wouldn't it be nice
if the relevant scripts allowed this? All that is needed is that they
use /etc/X11/app-defaults/Foo, if it
[EMAIL PROTECTED] said:
Please peruse /usr/doc/X11/debian.README, to understand why I say
that, on Debian, app-defaults files are not considered configurable.
For those who would like to specify their own application resource files,
you can set the environment variables
Michael Alan Dorman [EMAIL PROTECTED] writes:
If you disagree with this, as many seem to, please propose a solution
whereby package maintainers can easily make sure that app-defaults
files are updated to reflect any changes introduced in the upstream
app-defaults file.
Well, couldn't the
Hi!
I just browsed the Linux FSSTND (v1.2) but haven't found a comment about
the app-defaults directory.
Backups would be much easier if _all_ the configurable files are in /etc
and /usr can't be mounted readonly if one has to change the app-defaults
file. (Shouldn't, as a simple rule, all
Christian Schwarz [EMAIL PROTECTED] writes:
Backups would be much easier if _all_ the configurable files are in /etc
and /usr can't be mounted readonly if one has to change the app-defaults
file. (Shouldn't, as a simple rule, all files that are referred by the
debpkg-conffiles be placed in
16 matches
Mail list logo
