| 1 |
On Saturday 01 October 2005 14:01, Daniel Stiefelmaier wrote: |
| 2 |
> I'd like to introduce two ideas i had to improve portage. |
| 3 |
|
| 4 |
I haven't had an idea introduced to me that was new for at least a year.. |
| 5 |
Patches are more interesting. |
| 6 |
|
| 7 |
> sometimes i'd like to know something more about a package before i |
| 8 |
> emerge it. |
| 9 |
> |
| 10 |
> 1. release notes. (for the ebuild, not the application) |
| 11 |
> as a release notes file exists, a parameter could be used to show the |
| 12 |
> most recent entry. |
| 13 |
> maybe this fits "eix" better than "emerge" |
| 14 |
|
| 15 |
emerge --changelog ? |
| 16 |
|
| 17 |
> 2. advanced package info |
| 18 |
> most important here is an explanation of the available use flags. i know |
| 19 |
> there is a list of most flags (http://www.gentoo.org/dyn/use-index.xml) |
| 20 |
> but it is incomplete and doesnt explain some flags well. some have |
| 21 |
> different behaviour in different packages. |
| 22 |
> some flags are self-explanatory, but some are not. for example, the |
| 23 |
> "xprint" comment should say, that this is not necessary to print, and |
| 24 |
> under what circumstances it is needed. |
| 25 |
|
| 26 |
This should go to gentoo-dev@g.o as ebuild developers are the ones that decide |
| 27 |
what USE flags are available and how they're documented. |
| 28 |
|
| 29 |
> also, the advanced could provide |
| 30 |
> - links to howto's (like configuring apache) |
| 31 |
|
| 32 |
This is out of the domain of a package in any package management system IMO. |
| 33 |
|
| 34 |
> - list packages that are of use for this (plugins or utilized apps like |
| 35 |
> cervisia that integrates in quanta plus) |
| 36 |
|
| 37 |
Do you mean finding packages that depend on that package in question? |
| 38 |
|
| 39 |
> - tell how to contact the ebuild maintainer |
| 40 |
|
| 41 |
metadata.xml. This information is printed out when using -vv in |
| 42 |
portage-2.1_alpha. |
| 43 |
|
| 44 |
> that led my to another idea: a wiki for all ebuilds in portage. |
| 45 |
> all the information could then be in the wiki, and eix/emerge just print |
| 46 |
> the wiki-link. |
| 47 |
> i'd suggest mediawiki, as it has a discussion page attached. |
| 48 |
> maybe the wiki itself can only be changed by developers, and feedback is |
| 49 |
> given on the discussion page. |
| 50 |
|
| 51 |
Personally, I hate most wikis. 9 times out of 10, they are full of |
| 52 |
half-correct information. This makes them all the more dangerous as the |
| 53 |
"average Joe" can't tell what's correct and what isn't. |
| 54 |
|
| 55 |
> just some ideas, maybe needing some development, i hope you find them |
| 56 |
> useful. :) |
| 57 |
|
| 58 |
Ideas are "a dime, a dozen". |
| 59 |
|
| 60 |
-- |
| 61 |
Jason Stubbs |
| 62 |
-- |
| 63 |
gentoo-portage-dev@g.o mailing list |
Archives