| 1 |
Arun Raghavan wrote: |
| 2 |
|
| 3 |
> I was just wondering if this has been thought of before -- a lot of |
| 4 |
> ebuilds have a guide that should be read before/after installation. |
| 5 |
> For example, anybody emerge'ing bluez will probably want to read the |
| 6 |
> Gentoo Bluetooth Guide. Does it make sense to do something like this, |
| 7 |
> then: |
| 8 |
|
| 9 |
Yeah, Yoswink IIRC had a similar plan quite sometime back. Yoswink, |
| 10 |
would you please share the ideas/details? I'll try digging up IRC logs |
| 11 |
as well to see if I can come up with anything. |
| 12 |
|
| 13 |
> 1) add a RELATED_DOC variable to ebuilds to point to the related documentation |
| 14 |
|
| 15 |
I'm yet to read through your idea. Will do in a bit. |
| 16 |
|
| 17 |
AFAICS, the docs-team would be fine with this. I think we would need to |
| 18 |
work out a good plan, and then take it to the ebuild folks/list/IRC and |
| 19 |
see how we can work it out with them. |
| 20 |
|
| 21 |
I'm quite sure if we have a well thought out idea, people will be |
| 22 |
willing to think about implementing it. |
| 23 |
|
| 24 |
Regards, |
| 25 |
|
| 26 |
-- |
| 27 |
Shyam Mani | <fox2mike@g.o> |
| 28 |
docs-team | http://gdp.gentoo.org |
| 29 |
GPG Key | 0xFDD0E345 |
Archives