Hi,
- If I see a new package installed by someone else,
* if nothing depends on it, mark it Unknown; probably manually installed
* otherwise, mark it Unknown; probably automatically installed
Consider
apt-get install foo
apt-get remove foo
This leaves libfoo1, which was pulled in by foo and
On Wednesday 15 December 2004 09:01 am, Simon Richter wrote:
aptitude could be taught to have auto-installed being Yes,No or
Unknown. Whenever a package that is in Unknown state could be removed
if it were only installed as a dependency, aptitude should list them in
the actions to be performed
On Wed, Dec 15, 2004 at 01:53:20PM -0500, Daniel Burrows wrote:
On Wednesday 15 December 2004 09:01 am, Simon Richter wrote:
aptitude could be taught to have auto-installed being Yes,No or
Unknown. Whenever a package that is in Unknown state could be removed
if it were only installed as a
On Wednesday 15 December 2004 03:37 pm, Wouter Verhelst wrote:
It seems like Unknown would just be a synonym for No, right?
Uh, yes. I think.
You may want to explain that a bit more.
Well, from the bug report, it looks like the proposal is to maintain the
current behavior, but to set a
On Wed, Dec 15, 2004 at 04:02:03PM -0500, Daniel Burrows wrote:
On Wednesday 15 December 2004 03:37 pm, Wouter Verhelst wrote:
? It seems like Unknown would just be a synonym for No, right?
Uh, yes. I think.
You may want to explain that a bit more.
Well, from the bug report, it
On Wednesday 15 December 2004 07:51 pm, Wouter Verhelst wrote:
You may also want to set a flag on packages that are assumed to be
automatically installed, but of which you have no information.
aptitude never should assume that a package is automatically installed,
unless it performs the
6 matches
Mail list logo
