On Fri, 2003-07-25 at 11:19, Manoj Srivastava wrote:
> Not really. Why do we need this overly micromanaging rule in
> policy? As long as it understood that user data is not to be deleted,
> why can't I put user data in /var/lib// if I so desire, as long
> as I take care to not rm -rf that
On 25 Jul 2003 09:32:09 +0200, Thomas Hood <[EMAIL PROTECTED]> said:
> Re:
> 1. dpkg -L
> 2. conffiles belonging to the package
> 3. configuration files other than conffiles belonging to the package
> 4. package's log output, cached compiled versions of conffiles, etc.
> 5. user data created usin
Re:
1. dpkg -L
2. conffiles belonging to the package
3. configuration files other than conffiles belonging to the package
4. package's log output, cached compiled versions of conffiles, etc.
5. user data created using the package
On Fri, 2003-07-25 at 09:01, Manoj Srivastava wrote:
> > Here is my
On 21 Jul 2003 11:44:35 +0200, Thomas Hood <[EMAIL PROTECTED]> said:
> Actually we need to notice one more type of file than Emile did in
> http://marc.theaimsgroup.com/?l=debian-devel&m=105822874604492&w=2 ,
> namely, configuration files that aren't conffiles. Making the
> distinction above we
Hi, Roger Leigh wrote:
> For several reasons, it's not possible to know in advance how many files
> will be created, or what their names will be, so "rm -rf" is
> appropriate.
>
> For packages like dosemu, this is not (currently) appropriate. There is
> no technially valid reason for doing this,
Thomas Hood <[EMAIL PROTECTED]> writes:
> Here is my suggestion for how purge should be handled. Purge
> would delete #1 through #4 _and_ everything in /var/lib//.
> User data created using the package must then not be stored in
> /var/lib// but somewhere else, e.g., in someone's home
> directory
6 matches
Mail list logo
