SaroEngels (Talk | contribs) (emerge thoughts) |
SaroEngels (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | Issues with emerge | + | == Issues with emerge == |
for system dependent parts emerge should rely on the kdewin-installer package | for system dependent parts emerge should rely on the kdewin-installer package | ||
*make the kdewin-installer work on the commandline and integrate into emerge | *make the kdewin-installer work on the commandline and integrate into emerge | ||
| Line 5: | Line 5: | ||
*test for kdewin-* applications before using them | *test for kdewin-* applications before using them | ||
| − | Some more functions that are needed | + | == Some more functions that are needed == |
*find a better solution what to build (accept multiple targets at the commandline like the original emerge does) | *find a better solution what to build (accept multiple targets at the commandline like the original emerge does) | ||
*implement an update command which either updates the installed packages or which updates one package only | *implement an update command which either updates the installed packages or which updates one package only | ||
*make two packages possible: 'emerge-bin' and 'emerge-portage'. | *make two packages possible: 'emerge-bin' and 'emerge-portage'. | ||
*use another way to update the portage directory in future (rsync or similar) | *use another way to update the portage directory in future (rsync or similar) | ||
| + | |||
| + | == junior jobs == | ||
| + | * there seem to be tons of options that were added but not yet documented - if someone has nothing to do or if you want to understand emerge better, you should start and document those options | ||
| + | The options are defined in emerge/bin/emerge.py so you should be able to find out easily | ||
for system dependent parts emerge should rely on the kdewin-installer package
The options are defined in emerge/bin/emerge.py so you should be able to find out easily
KDE TechBase 