Randy Barlow wrote:
7v5w7go9ub0o wrote:
OTOH, the good news is that a newbie like me can install an outdated
package (e.g. Vidalia); resolve dependencies; uninstall the portage
version; download and compile the current version from the developer.
If you know how to do those things, learning how to make the ebuild that
does it isn't that much more to do. Then, instead of just filing the
bug report, you can submit an ebuild as a suggested fix with it and help
out. Linux works best when the users take part in it!
Fair enough!
My concerns with this, other than my abilities, are:
1. Showing proper respect to the guy who pioneered the effort to date,
and who may simply be out of town. (This disrespect would be alleviated
if there was an official policy encouraging "volunteer ebuilds".)
2. He won't be there to proofread my work anyway, so therefor my ebuild
would still not get into the disribution. (This could be alleviated if
there was a "designated backup" for each package - someone who could
either temporarily fill, or accept a "volunteer ebuild", and move it
forward.
It would also be nice if there was a single, "temporary homeless" list
of ebuilds belonging to folks who will be out of town for a while - this
would be a "one-stop" page to notify designated backup people, and
others who could keep an eye on the distributions.)
3. If a volunteer ebuild isn't proofread, it could contain a bug. (you
don't know me.)
P.S. A good place to start in writing an e-build for a new version of a
package is to use the ebuild for the old version ;)
I'll do that; and I'll also look forward to the reply to b.n.'s request.
--
[EMAIL PROTECTED] mailing list
