| 1 |
7v5w7go9ub0o wrote: |
| 2 |
> My concerns with this, other than my abilities, are: |
| 3 |
|
| 4 |
> 1. Showing proper respect to the guy who pioneered the effort to date, |
| 5 |
> and who may simply be out of town. (This disrespect would be alleviated |
| 6 |
> if there was an official policy encouraging "volunteer ebuilds".) |
| 7 |
|
| 8 |
It's not disrespectful, IMO, to do something that you don't see getting |
| 9 |
done. Especially since it's less work for another guy. I wouldn't |
| 10 |
worry about that point. |
| 11 |
|
| 12 |
> 2. He won't be there to proofread my work anyway, so therefor my ebuild |
| 13 |
> would still not get into the disribution. (This could be alleviated if |
| 14 |
> there was a "designated backup" for each package - someone who could |
| 15 |
> either temporarily fill, or accept a "volunteer ebuild", and move it |
| 16 |
> forward. |
| 17 |
|
| 18 |
This can happen. I've submitted ebuilds for backuppc-3.0.0, and so have |
| 19 |
many other people. In fact, the bug for it has several ebuilds that |
| 20 |
have been submitted but haven't made it into the official tree. I think |
| 21 |
that particular bug report might not be getting attention from the right |
| 22 |
people or something. That doesn't mean it isn't worth doing though, |
| 23 |
because people can still use the ebuild from the bug report. Ideally, a |
| 24 |
dev would see that, check it out for correctness, and add it to ~arch. |
| 25 |
|
| 26 |
Does anybody know how to call attention to a bug report that doesn't |
| 27 |
seem to have any devs paying attention to it? I think BackupPC is a |
| 28 |
fine product, and would like to see it in the tree for others to use. |
| 29 |
I'm using my own ebuild successfully, as are many of the fine folks who |
| 30 |
have contributed on that bug report. I'd just like my and others' |
| 31 |
efforts to be something that benefits more of the Gentoo community :) |
| 32 |
|
| 33 |
> 3. If a volunteer ebuild isn't proofread, it could contain a bug. (you |
| 34 |
> don't know me.) |
| 35 |
|
| 36 |
I don't think an ebuild would make it into the tree without being |
| 37 |
checked by a dev, and that's not what I am suggesting. I'm suggesting |
| 38 |
taking the burden of writing ebuilds off of the devs' shoulders so they |
| 39 |
can spend more of their time checking. Ebuilds for the majority of |
| 40 |
packages are pretty simple anyways, especially packages that just need a |
| 41 |
./configure && make && make install, so getting a bad bug in the ebuild |
| 42 |
itself isn't going to be that hard to avoid. |
| 43 |
|
| 44 |
-- |
| 45 |
Randy Barlow |
| 46 |
http://electronsweatshop.com |
| 47 |
-- |
| 48 |
gentoo-user@g.o mailing list |
Archives