Mailinglist Archive: zypp-devel (83 mails)
|< Previous||Next >|
[zypp-devel] [Fwd: [yast-devel] introduce a package history to remove obsolete packages]
- From: Lukas Ocilka <lukas.ocilka@xxxxxxx>
- Date: Mon, 09 Jun 2008 09:27:23 +0200
- Message-id: <484CDB5B.20008@xxxxxxx>
FYI, Forwarding from yast-devel: This rather sounds libzypp-related.
--- Begin Message ---
I use yast in openSUSE 10.3 to manage my software packages. I like to explore
- From: Hanno Svoboda <hs403@xxxxxxxxx>
- Date: Fri, 6 Jun 2008 20:33:46 +0100
- Message-id: <200806062033.46330.hs403@xxxxxxxxx>
many different FLOSS projects and install quite a lot of software which I
remove later on. A big problem for me is that my installation becomes more
bloated after a while, because libraries and dependencies which came with the
installed software can't be identified and are not automatically removed
(probably for a good reason). Therefor I like to propose an idea, which could
potentially solve this issue:
1. Create a history of installed packages with following information:
Package X was installed, also packages Y + Z were installed
2 If the user removes X, Y, or Z, YAST should asks: Should the other two
packages (X, Y and/or Z) also be removed as they have no other dependencies?
3. If the user decides not to remove them or they have dependencies on W
a different installation time point, they should be tagged as potentially
4. Removal of W should trigger again: Should Y and Z also be removed as
have no other dependencies and were marked as potentially obsolete?
5. If further dependencies exist or the user decides to keep them,
at 3. Either the loop ends in package removal or at stable state 3.
I hope this is not too confusing and this package bloating issue can be
tackled. I am happy to clarify or maybe somebody else has a better (simpler)
idea. If you think that sort of makes sense, you can read on some refinements
PS: Unfortunately, I cannot program and can't produce any poof of principle
implementation. I think their is no big logical error in it, but I am sure it
needs some polishing here and there.
REFINEMENTS to the idea above, which make it more complicated and powerful.
Points 2, 4 and 5 remain as they are.
1. Make a history of installed packages, which hold following
When Package X was installed, also packages Y + Z were installed which are in
an dependency relation to X.
If the dependency criterion is not used, unrelated software that was installed
at the same time (e.g. two completely unrelated programs) would fall under the
removal category, which is unwanted.
3. If the user decides not to remove them they should be tagged as
potentially "obsolete without dependencies". If they have dependencies on W
from a different installation time point, they should be marked as "obsolete
with dependencies". The user could use an option in YAST to remove all
obsolete packages in the installation which are tagged "obsolete without
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
--- End Message ---
|< Previous||Next >|