| 1 |
sometimes its nice to see what a package does ... and i mean more than a |
| 2 |
1-liner ... for example the way rpm stores a large description in itself ... |
| 3 |
|
| 4 |
i like having the 1-liner short description, dont get me wrong ... i dont want |
| 5 |
to see that change ... but what if we were to add support for a large |
| 6 |
description/explanation for ppl who are not familiar with it ... |
| 7 |
|
| 8 |
could be handled in a couple of ways: |
| 9 |
1. a package you would emerge that would have a large database of descriptions |
| 10 |
... not very good idea due to updating 1 package means a whole new d/l ... |
| 11 |
2. a package that would query a remote gentoo server via http or something |
| 12 |
3. another file for all packages to be added to cvs ... say 'Info' or 'About' |
| 13 |
or something similar ... i would rather not see it go into the ebuild ;) |
| 14 |
|
| 15 |
<[Eazy|E]> is there a way to get an info about the package, the info like the |
| 16 |
freshmeat.net gives out ? |
| 17 |
<[Eazy|E]> I liked the way rpm's had info stored about the package, so one who |
| 18 |
does not know the package can get an overview of the package with the text |
| 19 |
w/o checking the homepage etc |
| 20 |
<[Eazy|E]> since qpkg can query the packages, it could be used also for giving |
| 21 |
more info about the package, like -i, maybe just another flag that will spit |
| 22 |
out more text etc. |
| 23 |
|
| 24 |
thoughts/etc... ? |
| 25 |
-mike |
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives