| 1 |
Hi! |
| 2 |
|
| 3 |
I'd like to introduce two ideas i had to improve portage. |
| 4 |
|
| 5 |
sometimes i'd like to know something more about a package before i |
| 6 |
emerge it. |
| 7 |
|
| 8 |
1. release notes. (for the ebuild, not the application) |
| 9 |
as a release notes file exists, a parameter could be used to show the |
| 10 |
most recent entry. |
| 11 |
maybe this fits "eix" better than "emerge" |
| 12 |
2. advanced package info |
| 13 |
most important here is an explanation of the available use flags. i know |
| 14 |
there is a list of most flags (http://www.gentoo.org/dyn/use-index.xml) |
| 15 |
but it is incomplete and doesnt explain some flags well. some have |
| 16 |
different behaviour in different packages. |
| 17 |
some flags are self-explanatory, but some are not. for example, the |
| 18 |
"xprint" comment should say, that this is not necessary to print, and |
| 19 |
under what circumstances it is needed. |
| 20 |
|
| 21 |
also, the advanced could provide |
| 22 |
- links to howto's (like configuring apache) |
| 23 |
- list packages that are of use for this (plugins or utilized apps like |
| 24 |
cervisia that integrates in quanta plus) |
| 25 |
- tell how to contact the ebuild maintainer |
| 26 |
|
| 27 |
that led my to another idea: a wiki for all ebuilds in portage. |
| 28 |
all the information could then be in the wiki, and eix/emerge just print |
| 29 |
the wiki-link. |
| 30 |
i'd suggest mediawiki, as it has a discussion page attached. |
| 31 |
maybe the wiki itself can only be changed by developers, and feedback is |
| 32 |
given on the discussion page. |
| 33 |
|
| 34 |
just some ideas, maybe needing some development, i hope you find them |
| 35 |
useful. :) |
| 36 |
|
| 37 |
greets, Caliga |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-portage-dev@g.o mailing list |
Archives