On 05-20-2024 09:54AM, Andrei Borzenkov wrote:
On 20.05.2024 16:45, -pj via openSUSE Users wrote:
On 05-20-2024 01:37AM, Andrei Borzenkov wrote:
On Mon, May 20, 2024 at 8:43 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am wondering about how I should best go about purging packages and possibly dependencies along with what is displayed after passing 'zypper pa --unneeded'.
Why? What problem are you trying to solve?
I would like to remove packages that are bloating the machine. So that I can keep the machines package structure well organized.
Whack a mole ... then it is arguably makes more sense to start with --no-recommends and only add what you need.
... Why is "--no-recommends" not the default behavior then?
If removing the dependencies along with the package is set/selected. Will possibly other necessary important packages be affected by the removal of the dependency packages displayed by 'zypper pa --unneeded'?
Define "important".
If "important" stands for "some other package has dependency on this package" - no, it will not happen.
I believe that what you say in the last sentence above was my meaning of "important" is this situation. I should have probably made that much more clear. Why is 'solver.cleandepsOnRemove = true' not the default in Tumbleweed?
If "important" stands for "I (user) find the content of this package very important" - neither zypper nor RPM can read your mind. If this package has been explicitly installed, it will not be removed. But if it was added as dependency and then you found it useful - zypper has no way to know it.
Yes, i+ means the package has been manually installed by user/s I believe. What you say in the above paragraph > "But if it was added as dependency and then you found it useful". I believe this does not happen very often at all unless it is a package that is being developed or modified by machines user from what the package contents are in a configured current repo list. Then the package/s can be locked to prevent removal or change? When a 'zypper dup' is envoked, I believe zypper goes through the steps of checking the accessible installed packages installed in the OS of the machine against the packages contained in the repositories the machine has currently enabled.
This is usual pitfall of using human meaningful words in computer science. They do not mean what you expect them to mean.
Thank you for your insight. Please do respond with corrections. -Best Hopes