Development/Distro tools enhancement
From Mandriva Community Wiki
Contents |
[edit] Distro tools enhancement
This page intends to gather the requirements for enhanced distro tools, based on the work achieved within the EDOS project.
For each tool below, the objective is to describe roughly the algorithm used, the problems raised and some improvement ideas, so that the EDOS team can possibly take over and propose some solutions.
[edit] mkcd2/ng/whatever
Here is how mkcd should work:
An independent program reads directives and selects packages from a repository. It produces an extensive list of the packages to put on the CD.
A program fills the media directories (x84_64/main/release for example) with the packages selected previously.
A program prepares the media with product metadata (product.id, hdlist/media.cfg stuff, etc.)
A program writes the files into a CD.
Each program can be called separately with different options. A shell script automates the different steps to produce the equivalent of mkcd.
A smart configuration file should enable the production of the different ISOs by stacking pieces together, so that a pwp+ is the combination of medias (previously generated and checked) coming from "inferior" products (containing less media, i.e. less packages).
[edit] Usage scenario
1. the release manager defines packages to include by selecting them through 2 means: rpmsrate categories, direct package names (with regexps)
Note: the first "selector" program should also support
During development time, the automated script can be used. When approaching freeze time, the list of packages and dependency selection can be frozen and the 1st program is not called anymore, rather a copy of the generated list is used.
See also mkcd for an overview of the old mkcd.
[edit] rpmsrate
[edit] compsuser
... to be completed
