[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [RFD]: Question regarding actions to take on --purge of a package.



On 30-Jan-00, 01:15 (CST), Brock Rozen <brozen@torah.org> wrote: 
> On Sat, 29 Jan 2000 at 22:14, Steve Greenland wrote about "Re: [RFD]:...":
> > No, "purge" means what it says in dpkg(8):
> > 
> >  purge  The package is selected to be purged (i.e. we  want
> >         to remove everything, even configuration files).
> > 
> > Note the use of the word "everything".
> 
> Well, the logs weren't created upon installation -- then why do they get
> automatically removed upon "purge" ? That's the difference between the
> config files (with even 100 hours of work put into them...they were STILL
> created when the package was created). 

Just to be annoyingly nitpicky, not necessarily. There are lots of
packages whose configuration files are optional, and whose non-existence
is acceptable, but that are none-the-less configuration files of that
package and are removed upon purge.


> > Then don't use purge. Use remove. That should preserve config files and
> > logs If it doesn't, the package has bug.
> 
> And if I want to save just the logs? There IS something inherently
> different with saving just the logs and nothing else (including config
> files)

Then *copy* the *$#@! precious log files somewhere else before you
purge. There is nothing inherently different: purge says "remove all
traces of this package, I'm getting rid of it permanently".

If the data is that valuable, back it up. But for 99.9% of packages, log
files are not data, and of no use once the package is purged.

Steve

-- 
Steve Greenland <vmole@swbell.net>
(Please do not CC me on mail sent to this list; I subscribe to and read
every list I post to.)


Reply to: