> Would you expect removing vi to remove all the files you created with
> it? "Purge" means remove the configuration files that the package
> installed in addition to all the other files from the package.
Agreed, and I am not surprised that this happens. My intent for asking the
question was to kn
Kushal Koolwal writes:
> Is there a Debian package rule which says "only remove files which
> were originally provided by the package"...
Would you expect removing vi to remove all the files you created with
it? "Purge" means remove the configuration files that the package
installed in addition t
> This sounds logical, since your out-of-tree modules are probably still
> there.
Yeah that's right. But why doesn't it (apt-get purge) remove those out-of-tree
modules also when I try to remove the package? Is there a Debian package rule
which
says "only remove files which were originally pro
On 2009-08-13 21:51 +0200, Kushal Koolwal wrote:
> In a normal scenario, whenever we do:
>
> apt-get purge linux-image-
>
> the corresponding:
>
> /lib/modules/
>
> directory gets removed from the system.
>
> But I noticed that suppose installed some out-of-tree kernel modules
> and now when you t
In a normal scenario, whenever we do:
apt-get purge linux-image-
the corresponding:
/lib/modules/
directory gets removed from the system.
But I noticed that suppose installed some out-of-tree kernel modules and now
when you try to remove the same kernel (for which you installed out-of-tree
5 matches
Mail list logo
