1 |
hi all, thanks for a great distro! |
2 |
|
3 |
now, I'm in the process of trying to contribute a little, in effect |
4 |
making some ebuilds. now, the technical writing of the builds isn't |
5 |
a problem, yet, it's more a few things I wonder about policy-wise. |
6 |
|
7 |
first off, if I see an ebuild that is out of date, do I contact the |
8 |
author of the out-of-date ebuild or do I submit a new one? so far |
9 |
I've thought "if the old one is _really_ out of date, I'll submit a |
10 |
new ebuild, if it's a week or two since the new version came out, |
11 |
I'll take it with the author." the real question is probably how |
12 |
"possessive" authors are / are supposed to be with regards to their |
13 |
ebuilds. is there any set policy on this? |
14 |
|
15 |
second, and a bit more tricky. I thought I'd make an xgammon |
16 |
ebuild. all fine and dandy, but there are a few patches (from |
17 |
RedHat) to xgammon which are nice to have (they fix minor bugs -- |
18 |
void main -> int main and a few other things). what to do? if I |
19 |
include the patches, how do I link to them? or do I just put them |
20 |
in the "files"-directory with the ebuild? |
21 |
|
22 |
anyhow, thanks for your time, hopefully you won't need to thump my |
23 |
head too many times in the future. |
24 |
|
25 |
-- |
26 |
Terje - a very happy Gentoo-user, hopefully contributing a little |
27 |
eventually. |