On Tue, Nov 29, 2005 at 10:31:14AM -0600, Daniel Burrows wrote: > In that case, it's expected behavior (aside from it getting set to false, > of course). Aside from editing the file manually, all that I know of that > would do this is deactivating the "automatically resolver dependencies of a > package when it is selected" option in the Options -> Dependency Handling > dialog.
I have that disabled for months, because I like to see what I am installing when I am working with aptitude interactively. On the command line, it's ok to have the dependencies automatically resolved since one sees what is installed immediately. It is still not clear for my why the behavior has so suddenly changed, neither in sync with a config change on my part nor with a new aptitude version. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
