| 1 |
Hi Ben! |
| 2 |
|
| 3 |
* Ben Lutgens assembled some ascibets to say: |
| 4 |
Ben >Hi all, I am proposing we add a new file to the portage tree directories. I |
| 5 |
Ben >was thinking something like the pkg_descr files in freebsd ports. It could |
| 6 |
Ben >have a slightly more detailed description, the install process ( from the |
| 7 |
Ben >portage point of view ) as well as homepage and ftp urls and possibly a |
| 8 |
Ben >brief gentoo-changelog. It could look something like this. |
| 9 |
Ben >I just think it'd be nice to have a file that we can less to find out what |
| 10 |
Ben >a package is, sometimes the name isn't enough as I can't possibly keep |
| 11 |
Ben >straight everything and the DESCRIPTION in the ebuild isn't great since |
| 12 |
Ben >noone wants to clutter everything up. |
| 13 |
Ben > |
| 14 |
Ben >I'm also not suggesting we take the next 3 months to write these for the |
| 15 |
Ben >existing packages, just adding them for new ones or possibly when updating. |
| 16 |
|
| 17 |
I'm all for it. |
| 18 |
|
| 19 |
also it would be nice if it could be interactive in way that when : |
| 20 |
|
| 21 |
emerge foo.ebuild |
| 22 |
it shows the pkg_descr() |
| 23 |
thenruns the emerge --pretend foo.ebuild |
| 24 |
and then asks the user whether to go ahead or not ? |
| 25 |
|
| 26 |
and the user can bypass the interactivity by passing one more parameter as : |
| 27 |
emerge --nopretend foo.ebuild |
| 28 |
|
| 29 |
which shows the pkg_descr() |
| 30 |
and then goes ahead and merges the pkg. |
| 31 |
|
| 32 |
best regards, |
| 33 |
|
| 34 |
pm |
| 35 |
-- |
| 36 |
Developer <pm@g.o> |
| 37 |
Gentoo Linux http://gentoo.org |
| 38 |
|
| 39 |
#exclude <windows.h> |
Archives