For developers: ebuild creation questions

[Pythonhead]

Hello,

I've read the ebuild HOWTO (http://www.gentoo.org/doc/en/gentoo-howto.xml). A great deal of it is geared towards official Gentoo developers who do the actual cvs commits of ebuilds.

I'm working on a more concise quickstart for user-submitted ebuilds. I'm writing this as part of the documentation for my ebuild GUI editor (http://abeni.sf.net/) and will also submit it to the Documentation, Tips & Tricks forum.

It explains how to use bugzilla to submit an ebuild.

For the Gentoo developers out there, can you suggest anything that would help you with processing user-submitted ebuilds?

Are there common mistakes in user-submitted ebuilds that you can tell us how to avoid?

Should the users change anything in the header comments if they are simply "bumping up" an ebuild from a previous version?

Any other "do's and don'ts" of ebuild creating?

Thanks

[beowulf]

There was a thread on gentoo-dev about just this thing... i'm not sure if the discussion is archived somewhere, but if it is, find the thread: "common ebuild mistakes"

The original post has a link to this page: http://cvs.gentoo.org/~liquidx/ebuildmistakes.html
_________________
I have nothing witty to say here... ever

[Pythonhead]

Wow. Thanks, that is exactly what I needed.

[frbie]

Hello,

ist the ebuild gui still alive?

I tried the cvs commands on the website but it faildes with this error message:

cvs login: warning: failed to open /root/.cvspass for reading: No such file or directory
root@Gentoo atlan # cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/abeni login
Logging in to :pserver:anonymous@cvs.sourceforge.net:2401/cvsroot/abeni
CVS password:
cvs [login aborted]: end of file from server (consult above messages if any)
root@Gentoo atlan # cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/abeni co abeni
cvs [checkout aborted]: end of file from server (consult above messages if any)