Ubuntu Studio LiveDVD
Ubuntu Studio should transition to providing a LiveDVD for installation medium.
Additionally, providing a GUI selection of additional packages during installation based on work flows would add extra functionality (see: http://
Lastly, Ubuntu Studio will drop the alternate installation image.
Blueprint information
- Status:
- Complete
- Approver:
- Scott Lavender
- Priority:
- Medium
- Drafter:
- Scott Lavender
- Direction:
- Approved
- Assignee:
- Ubuntu Studio Development
- Definition:
- Approved
- Series goal:
- Accepted for precise
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Scott Lavender
- Completed by
- Scott Lavender
Related branches
Related bugs
Bug #695892: no live CD for ubuntustudio | Fix Released |
Bug #840144: Use recommends instead of depends in seeds | Fix Released |
Sprints
Whiteboard
To accomplish both goals we can make use of what Edubuntu has already done, both with their dvd-live seed (1) and their Ubiquity patch (2).
Work items:
[cjwatson] livedvd - review edubuntu 'dvd-live' seed: DONE
[cjwatson] livedvd - create appropriate Ubuntu Studio seeds: DONE
[slavender] build - inform 'cd image team'(5) of live dvd plans: DONE
[cjwatson] build - enable live DVD build for Ubuntu Studio: DONE
[ubuntustudio-dev] build - wait for image to build and test live dvd with patched ubiquity: DONE
[slavender] ubiquity - convert metapackages from 'depends' to 'recommends' (4): DONE
[knome] ubiquity - add content to ubiquity-
[astraljava] ubiquity - review edubuntu's ubiquity plugin (2): DONE
[astraljava] ubiquity - copy/modify plugin to our bzr branch (see "notes below") (2): DONE
[slavender] ubiquity - define work flows for user selected components: DONE
[slavender] ubiquity - update seeds to represent work flows (3): DONE
(1) http://
(2) http://
(3) https:/
(4) https:/
(5) https:/
http://
"notes below"
To customize it and reuse it in a different distro, one has to change the following:
* BEFORE and AFTER flags, to place the screen at the right stage
* src_pkg - the metapackage to be parsed (usually seed packages, e.g. edubuntu-meta, ubuntustudio-meta, etc)
* meta_blacklist - the metapackages that won’t be shown in the list (they appear as collapsible categories in the list; e.g. edubuntu-server is blacklisted and edubuntu-desktop is not; in Ubuntu Studio ubuntustudio-
* package_blacklist - the packages that won’t be shown in the list (e.g. unity-2d)
Changing the NAME declaration is not required, but might be useful.
Things like relation_blacklist don’t have to be altered.
You will probably have to ship custom translation files, too.
This system (obviously) requires the metapackages to use “Recommends:” instead of “Depends:” for all apps which the user can choose to include or not to include. All dependencies are blacklisted automatically for your convenience.
Work Items
Dependency tree
* Blueprints in grey have been implemented.