content snap dependency management
Bug #1711329 reported by
Jonathan Riddell
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Fix Released
|
High
|
Michael Vogt |
Bug Description
In KDE land we are creating Snaps for KDE Applications. These all use Qt and KDE Frameworks which is a lot of duplicated disk space if included in every Application. So we have split these out into an isolated snap kde-frameworks-5. However this must be installed prior to the application else it doesn't work.
snapd should include a method of dependency tracking for when snaps need another snap installed first.
affects: | snapcraft → snapd |
To post a comment you must log in.
Agreed, this is a priority to make a great desktop experience.
At the moment I've seen two paths discussed:
* stacks (where the name being installed is a YAML description of a
set of snaps and plugs connecting them)
* deps (where the store knows to send the extra snap and the device
knows that's OK)
In both cases the user should just ask for what they want ("snap install
krita") and everything else Just Works.
Thoughts?
Mark