On Wed, Aug 27, 2008 at 11:02:08AM +0300, "Eugene V. Lyubimkin" <[EMAIL PROTECTED]> was heard to say: > Rob Gom wrote: > > Hello, > > is this bug in aptitude when I try: > > $ aptitude install a > > [...] > > b will be removed > > $ aptitude install a b > > [...] > > b will be removed > > [OK] > > $ aptitude install b > > [b is installed fine, the same with a] > > > > So why does aptitude want to remove package b in the first place?
[snip] > Aptitude tries to remove automatically installed packages. If you > manually install them, aptitude won't try to do this. It's not a bug. It is interesting that "install a b" doesn't flag "b" as manual. The command-line parsing logic is hairy and tries to "do the right thing" in various cases, but this one seems to be falling through the cracks (due to when aptitude calculates unused removals). Problem is, I'd have to be careful adding code to handle this situation: the command-line is one of the few parts of aptitude that's not very well specified, and so I'm not sure exactly what would happen if I tried various hacks to do what you (quite reasonably) expect here. I don't see any obvious problems, but it's entirely possible that some other use case would be affected. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
