Re: [gentoo-dev] flame: complaint about being ignored.

[Wade Nelson]

Corvus Corax wrote:

 > well of course I dont really start a flame war, so I hope its not 
inevitable ;)
 >
 >
 > I asked some questions here 3 months ago, about how DEPENDs in an ebuild
 > can be formatted, when some software can use either of 2 libraries, 
to build and
 > run, but not both at the same time, and both libs have their own useflag.
 >
 > well I got some answers, tried them out, and it didnt work with 
strange errors
 > (probably portage caused, but dunno), then I used an approach which 
someone told
 > me to be "deprecated", and it worked flawlessly :)
 >
 > I submitted the ebuild to bugs.gentoo.org
 > bug #47130
 > http://bugs.gentoo.org/show_bug.cgi?id=47130
 > http://bugs.gentoo.org/attachment.cgi?id=29012&action=view
 >
 > which then laid idle for over 3 months and is still not in the 
portage tree
 >
 > so my slightly impatient question, why is it being ignored? If it 
doesnt conform
 > with some convention or has bugs, please tell me, i can fix that.
 >
 > Motiontrack is my own project, so its no problem for me to release or 
modify
 > the ebuild for new motiontrack versions when I release them, this way
 > maintaining the ebuild.
 >
 > hell that project is even developed under gentoo linux, it'd be a 
shame if
 > theres no ebuild for it.
 >
 >
 > Corvus Corax
 > aka Eric Noack
 >
 > (aka "gentoo" in bugzilla, thats because i thought that name field 
would be the
 > "password" field, without reading the form properly *duck* ;)
 >
 >

Sometimes its not a matter of being ignored, its a matter of time 
constraints. Gentoo developers are volunteers, and even with new devs on 
a fairly regular basis, there aren't necessarily enough devs to take on 
every new piece of software while still properly maintaining existing 
packages... I also have some ebuilds idling in bugzilla, but priorities 
lie with making sure existing packages are performing as intended, and 
bugs are being handled in an effective manner for said packges. Taking 
on a new package is ineveitably increasing the demands of the often (if 
not always) strained developer.  On a side note, you could always 
utilize the proper channels to become a dev... Even if you only maintain 
your own packages, it would hopefully ensure that those packages are of 
the highest quality, and squashing a few bugs on the side never hurts :)

Cheers
--Wade

PS: I'm not saying your package or any other isn't worth the time of the 
developers, there's often just not enough time to go around.


--
gentoo-dev@g.o mailing list