On Tue, 3 Jun 2008 21:05:30 +0200
Michael Koch [EMAIL PROTECTED] wrote:
So a good installer knows when you mount your $HOME on multiple machines
and use some config files only on some machines? /irony
Its the job of the user to cleanup his home. He knows best what he still
needs. Or at
Andrea Bolognani [EMAIL PROTECTED] writes:
Its the job of the user to cleanup his home. He knows best what he still
needs. Or at least should know.
When you have a lot of software installed on your system, it might get
difficult to trace exactly which configuration files you need and which
On Wed, 04 Jun 2008 12:16:40 +0200
Reinhard Tartler [EMAIL PROTECTED] wrote:
When you have a lot of software installed on your system, it might get
difficult to trace exactly which configuration files you need and which
ones you don't need.
Which is a good reason to use software that
Richard Kettlewell writes (What should postrm purge actually do?):
Is it written down anywhere what postrm purge is supposed to do?
Presumably remove some set of files, but what criteria should be used to
choose which?
Things I'm uncertain about, that someone might actually miss
ke, 2008-06-04 kello 13:38 +0200, Jeremiah C. Foster kirjoitti:
I think removing log files is a bad practice. A user may need to keep
those log files (by law for example) and unbeknownst to them, debian
has removed them when they removed web server X to replace it with
web server Y.
In that
Lars Wirzenius [EMAIL PROTECTED] writes:
ke, 2008-06-04 kello 13:38 +0200, Jeremiah C. Foster kirjoitti:
Log files should be out of bounds, even for --purge.
Doing that would mean log files never get cleaned up, unless the
sysadmin realizes that they need to it manually. That's not a good
On Wed, Jun 04, 2008 at 01:38:30PM +0200, Jeremiah C. Foster wrote:
Richard Kettlewell writes (What should postrm purge actually do?):
Things I'm uncertain about, that someone might actually miss:
- log files
Yes, these should be removed.
I think removing log files is a bad
On Wed, Jun 04, 2008 at 02:20:08PM +0200, Goswin von Brederlow wrote:
Lars Wirzenius [EMAIL PROTECTED] writes:
ke, 2008-06-04 kello 13:38 +0200, Jeremiah C. Foster kirjoitti:
Log files should be out of bounds, even for --purge.
Doing that would mean log files never get cleaned up,
Did you consider the case with $HOME being mounted on NFS with
rootsquash (which is set by default)? Should the postinst then 'su' to
each user to do the modifcations in that case then? How about if some
extra security policy is active like apparmor or selinux?
Sorry, the only sane option which
Andrea Bolognani skrev:
When you have a lot of software installed on your system, it might get
difficult to trace exactly which configuration files you need and which
ones you don't need.
Now imagine the following situation: a package's maintainer can declare the
per-user configuration/cache
On Tue, Jun 03, 2008 at 08:58:54PM +0200, Jeffrey Ratcliffe wrote:
Fine. Although it always annoyed me that my $HOME filled up with
spurious dotfiles whose origin I'm not necessarily sure of, and that a
good installer could know to remove them if the package were purged.
If you run a shared
Frank Lichtenheld [EMAIL PROTECTED] writes:
On Wed, Jun 04, 2008 at 02:20:08PM +0200, Goswin von Brederlow wrote:
Lars Wirzenius [EMAIL PROTECTED] writes:
ke, 2008-06-04 kello 13:38 +0200, Jeremiah C. Foster kirjoitti:
Log files should be out of bounds, even for --purge.
Doing that
On Tue, 03 Jun 2008, Richard Kettlewell wrote:
Things I'm uncertain about, but that wouldn't be missed:
- infrastructural stuff (lockfiles, sockets, etc)
Probably. If the stuff isn't running anymore.
- files containing cached data
Things I'm uncertain about, that someone might
Is it written down anywhere what postrm purge is supposed to do?
Presumably remove some set of files, but what criteria should be used to
choose which?
The policy document is not much help; s6.8 says when it is called, but
not what it actually needs to do. I can't find more detail, though of
2008/6/3 Peter Palfrader [EMAIL PROTECTED]:
- data accumulated from users
Should I be doing something like
rm /home/*/.packagedotfile
for user-specific dotfiles?
I don't see this in the policy.
Regards
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
On Tuesday 03 June 2008 08:41:20 pm Jeffrey Ratcliffe wrote:
2008/6/3 Peter Palfrader [EMAIL PROTECTED]:
- data accumulated from users
Should I be doing something like
rm /home/*/.packagedotfile
for user-specific dotfiles?
for the love of flying spaghetti monster please no :)
a purge
2008/6/3 sean finney [EMAIL PROTECTED]:
a purge should only remove files that were installed by the package or
otherwise incidentally generated in FHS compliant locations. data created in
users' home directories is definitely outside such a scope. i.e., if dpkg
couldn't put files there, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/03/08 13:58, Jeffrey Ratcliffe wrote:
2008/6/3 sean finney [EMAIL PROTECTED]:
a purge should only remove files that were installed by the package or
otherwise incidentally generated in FHS compliant locations. data created in
users' home
Richard Kettlewell writes (What should postrm purge actually do?):
Is it written down anywhere what postrm purge is supposed to do?
Presumably remove some set of files, but what criteria should be used to
choose which?
It's a shame that this isn't more clearly documented.
The policy
On Tue, Jun 03, 2008 at 08:58:54PM +0200, Jeffrey Ratcliffe wrote:
Fine. Although it always annoyed me that my $HOME filled up with
spurious dotfiles whose origin I'm not necessarily sure of, and that a
good installer could know to remove them if the package were purged.
It's important to
Andreas Bombe wrote:
[...]
The user may have
imported the configuration from some other machine, or intend to use the
configuration elsewhere. The usefulness of user configuration is
therefore not tied to the installed state of the package on this system.
Particularly since the user may have
On Tue, Jun 03, 2008 at 08:58:54PM +0200, Jeffrey Ratcliffe wrote:
2008/6/3 sean finney [EMAIL PROTECTED]:
a purge should only remove files that were installed by the package or
otherwise incidentally generated in FHS compliant locations. data created in
users' home directories is
22 matches
Mail list logo
