(Please CC me, I'm not subscribed).
First of all, I'll warn you that I use Ubuntu. Everybody is probably
tired of Ubuntu users asking for help here, but I think my question
applies equally well to Debian.
I'm struggling to understand the autoremoval behavior of aptitude 0.6.3.
Let's say I
On 2010-10-11 17:15 +0200, Gard Spreemann wrote:
First of all, I'll warn you that I use Ubuntu. Everybody is probably
tired of Ubuntu users asking for help here, but I think my question
applies equally well to Debian.
Yes, and I can reproduce your problem in Debian.
I'm struggling to
I'm struggling to understand the autoremoval behavior of aptitude
0.6.3. Let's say I have a virtual package A provided by A1 and
AFAIK, it gets autoremoved it it was automatically installed AND if
there are no other packages on the system that depend AND/OR recommend
it, depending on your
In 87lj64k59x@turtle.gmx.de, Sven Joachim wrote:
On 2010-10-11 17:15 +0200, Gard Spreemann wrote:
$ aptitude install gcc-4.5
The following NEW packages will be installed:
cpp-4.5{a} gcc-4.5 libmpc2{a}
*Snip*
$ aptitude remove gcc-4.5
The following packages will be REMOVED:
On Monday October 11 2010 19:28:42 Sven Joachim wrote:
Not necessarily. There may be other packages which depend on C | B, and
previously you had C installed but not B. In this case B is not unused.
Right, I didn't think of that. Thanks for clarifying.
Now this is interesting. Although
On Monday October 11 2010 19:52:35 Arthur Machlas wrote:
Does aptitude purge ~c get rid of them though?
No, it doesn't.
--
Gard Spreemann
spree...@math.ntnu.no, spree...@pvv.ntnu.no, gspreem...@gmail.com
http://folk.ntnu.no/spreeman
signature.asc
Description: This is a digitally signed
6 matches
Mail list logo
