On Mon, 29 Mar 1999, Mitch Blevins wrote:
> A counter field is totally )[M#R) from the Auto flag. Just because
> a package has no other packages depending on it does not mean that it
> should be removed. For example, xpilot is an excellent game, and I
> wouldn't want it removed... but
In foo.debian-user, you wrote:
> This sounds like a great idea.. I have one question tho:
>
> Foo depends on libfoo1 and libfoo2
> libfoo1 depends on foostuff1 and foostuff2
>
> So, say I remove foo, will it be smart enough to remove foostuff1 and
> footstuff2 as well as libfoo1 and libfoo2?
I
In a message dated 3/29/99 2:29:43 AM Central Standard Time,
[EMAIL PROTECTED] writes:
> Apt will keep a boolean flag called 'Auto' for each package installed
> on your system. 'Auto' is short for 'Automatically uninstall this
> package when it is not required anymore because of a dependency'.
In foo.debian-user, you wrote:
> On Mon, 29 Mar 1999, Mitch Blevins wrote:
> > Apt will keep a boolean flag called 'Auto' for each package installed
> > on your system. 'Auto' is short for 'Automatically uninstall this
> > package when it is not required anymore because of a dependency'.
>
> What
On Mon, 29 Mar 1999, Mitch Blevins wrote:
> Mark Phillips wrote:
> > [snip nice suggestion]
>
> This has already been discussed and is being addressed in apt.
> Here's how it will work (if I understand correctly):
>
> Apt will keep a boolean flag called 'Auto' for each package installed
> on yo
BENJAMIN FARRELL wrote:
>
> I assume that most of the dependences are going to be librarys, mybe it
> could be possible to have dpkg purge out any librarys that don't have
> anything depending on them. (or mybe some debian person could come up with
> some cmd line option for dpkg to do this :).
On Mon, Mar 29, 1999 at 01:09:20PM +0100, BENJAMIN FARRELL wrote:
> I assume that most of the dependences are going to be librarys, mybe it
> could be possible to have dpkg purge out any librarys that don't have
> anything depending on them. (or mybe some debian person could come up with
> some cmd
adBen)
-Original Message-
From: Mark Phillips <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org ;
debian-devel@lists.debian.org
Date: 29 March 1999 09:17
Subject: Suggestion for change to debian package format
>The debian package format is very nice and quite sophisticated, but I
>
Mark Phillips wrote:
> > Is that what you were looking for?
>
> Almost. This would work for "required" packages, but what about
> "suggested" packages?
>
> Perhaps dselect or the apt front end could behave the same (by
> default) with "suggested" packages, with the user being able to turn
> off
Has a more primitive method been considered (i.e., an option to dpkg
which tries to purge or remove stuff a package depends on)?
e.g., dpkg --remove|--purge [--excise]
--
On Mon, 29 Mar 1999, Mitch Blevins wrote:
> Mark Phillips wrote:
> > [snip nice suggestion]
>
> This has already been d
> Mark Phillips wrote:
> > [snip nice suggestion]
>
> This has already been discussed and is being addressed in apt.
> Here's how it will work (if I understand correctly):
>
> Apt will keep a boolean flag called 'Auto' for each package installed
> on your system. 'Auto' is short for 'Automatica
Mark Phillips wrote:
> [snip nice suggestion]
This has already been discussed and is being addressed in apt.
Here's how it will work (if I understand correctly):
Apt will keep a boolean flag called 'Auto' for each package installed
on your system. 'Auto' is short for 'Automatically uninstall th
The debian package format is very nice and quite sophisticated, but I
feel it lacks in one area. Let me illustrate.
Suppose I want to install a number of major application packages. In
the process of selecting them, dselect tells me, or suggests to me,
that I install a number of other packages.
13 matches
Mail list logo
