#3 Investigate other stray modules beyond installer
Opened 6 years ago by otaylor. Modified 6 years ago

We know that we don't want the installer module to be a dependency of the desktop modules - instead the installer should depend on the desktop-runtime module. But what about other modules that we are currently pulling in? Are there other cases where the dependency should be reversed, or packages should be moved to a common base. java for giflib definitely looks suspicious as krb5 for words. To fully investigate this probably requires some way (possibly just a text file dump) to see the module: packages-we-inherit-from-it relationship clearly.


Log in to comment on this ticket.

Metadata