Submitting ebuilds

This guide explains how to submit ebuild packages through the Bugzilla tracking system.

Create A Bugzilla Account
Point your web browser to http://bugs.gentoo.org. This is the URL for the Bugzilla bug tracking database. In the list of links, one of the items reads "Open a new Bugzilla account". If you have not done so already (e.g. for submitting a bug), click on this link and create a new account.

Don't Submit CPAN Ebuilds
Portage provides a tool called  which installs a given CPAN module on your Gentoo system using Portage, storing the necessary information (such as dependencies, provided files, etc.) in the Portage database, just like it would when you install an ebuild. It is therefore not needed (nor recommended) to submit CPAN ebuilds.

For more information on , please consult its man page.

Create a new bug
At the bottom of the main page or login page, there is a yellow box. Choose the  link. Or, you can just go to the URL http://bugs.gentoo.org/enter_bug.cgi. Either will bring you to the  page.

Bugzilla can track multiple products. For example, in Gentoo, other products may include documentation or tools used to administrate the website. From the list of products, Ebuilds should always be submitted to.

Clicking on the  product should bring up a new bug entry form.

Completing the bug form
The first field on the form is. If you know which version your package belongs in, set it here. Otherwise, select. Next, set the component. All ebuild scripts are of the component type.

The categories ,   , and   do not need to be set for ebuilds.

The  field should be set to.

Leave the  field blank. If you haven't changed Bugzilla's mail settings, you, as a reporter, will automatically receive email on bug updates.

Fill in the  field with a brief note of what package you are submitting and whether it's an update or a new submission. Something like the following is great:  or.

The  field should be filled in as completely as possible. Here's an example from Bug Number 7:

Example description

Once the summary is complete, click.

Attaching the Ebuild Script
After clicking  on the   page, you will go to the   page. Take note of the bug number.

Toward the bottom of this page, there is a link to. Click on this link.

Select the file using the text entry box or the  dialog. In the  field, type the name of the ebuild file, much the same as you did in the   section of the last page.

Make sure that the content type is set to "text/plain", and that the radiobutton for  is marked.

There are no other required fields on this form. Click  and you are done!

Dependencies
In cases where you might submit multiple ebuilds, and some of them depend on others, it is very helpful if these dependencies are noted. Viewing the bug again should allow you to enter another note. Please add dependancy information here.

Acknowledgements
We would like to thank the following authors and editors for their contributions to this guide:


 * Matt Butcher