Packages added by the dependency solver in order to resolve a user's request, are marked as having been automatically installed. They may later be removed, if no more manually installed packages depend on them (e.g. by zypper remove --clean-deps).

However things may go haywire. Automatically installed packages may turn out to be useful, and you may want to exclude them from any automatic cleanup. And vice versa.

For this you need to be able to inspect and manipulate a packages 'autoinstalled' property. This is what this project is going to provide.

Zypper search/info command output should distinguish between 'automatically' installed packages and those requested by the user, e.g. by using 'i' for automatically installed and 'I' for user requested packages.

2 new commands markauto/unmarkauto shall allow to change an installed packages 'autoinstalled' property.

Ihis is IMO the prerequisite if we want to provide more automatic cleanup commands.

Looking for mad skills in:

zypper

This project is part of:

Hack Week 15

Activity

  • over 2 years ago: blarson left Add zypper markauto/unmarkauto commands to allow tuning automated cleanup
  • over 2 years ago: blarson joined Add zypper markauto/unmarkauto commands to allow tuning automated cleanup
  • over 2 years ago: joachimwerner liked Add zypper markauto/unmarkauto commands to allow tuning automated cleanup
  • over 2 years ago: pluskalm liked Add zypper markauto/unmarkauto commands to allow tuning automated cleanup
  • over 2 years ago: mlandres added keyword "zypper" to Add zypper markauto/unmarkauto commands to allow tuning automated cleanup
  • Show History

    Comments

    • dmacvicar
      over 2 years ago by dmacvicar | Reply

      Would it make more sense to start turning zypper into a more subcommand kind of ui to avoid polluting the UX with tons of command?

      Like:

      zypper mark --auto or zypper mark auto

      (thing of git remote add vs git remoteadd)

    Similar Projects

    This project is one of its kind!