Create a system of metapackages
Having a metapackage system will allow installing all elementary components in other distros; in addition, currently there's no way to push post-release package set fixes (see bug #750534 or #748249 for example). It will also make ebuild script easier to maintain.
Having cascading metapackages (e.g. elementary-desktop depending on elementary-apps and elementary-look) will make the system even more flexible and easier to maintain.
Blueprint information
- Status:
- Complete
- Approver:
- elementary OS team
- Priority:
- Essential
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Sergey "Shnatsel" Davidoff
- Definition:
- Approved
- Series goal:
- Accepted for 0.2-luna
- Implementation:
-
Implemented
- Milestone target:
-
luna-beta1
- Started by
- Sergey "Shnatsel" Davidoff
- Completed by
- Sergey "Shnatsel" Davidoff
Related branches
Related bugs
Bug #755384: Make elementary-desktop package | Fix Released |
Bug #800847: Metapackage dependencies are not sufficient for a complete system | Fix Released |
Sprints
Whiteboard
everything is available in daily PPA.
We still need to include some things that are not yet packaged, like Plymouth, so not marking this implemented.
The whole system is now powered by seeds.
Which oppurtunities does that give us, we still dont have daily builds or something like that. --gotwig
gotwig: see https:/
Work Items
Dependency tree

* Blueprints in grey have been implemented.