| 1 |
Hi! |
| 2 |
|
| 3 |
With the new Issue tracker (Bugzilla) up and running ebuild submissions |
| 4 |
are done through it. All that has uncommited ebuilds (in gentoo-ebuild |
| 5 |
or in incoming/) please submit your ebuilds in the bugzilla. |
| 6 |
|
| 7 |
Sorry for the inconvinience but hopefully it'll go smother now since |
| 8 |
it's easier to see what needs to be done. |
| 9 |
|
| 10 |
And as always, if it's updates to ebuilds _PLEASE_ send a patch instead |
| 11 |
of the entire ebuild. |
| 12 |
|
| 13 |
HOWTO submit an ebuild: |
| 14 |
|
| 15 |
1) Create a bugzilla account if you don't have one: |
| 16 |
http://bugs.gentoo.org/createaccount.cgi |
| 17 |
|
| 18 |
2) Go to the enter new bug form: |
| 19 |
http://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%20Linux |
| 20 |
|
| 21 |
3) Choose Component Ebuild |
| 22 |
|
| 23 |
4) Add a Summary that tells which ebuild |
| 24 |
|
| 25 |
5) Write a description of the ebuild: |
| 26 |
Take a look at http://bugs.gentoo.org/show_bug.cgi?id=7 for a good |
| 27 |
example. The better a description you write the easier is it for us |
| 28 |
to take care of including it. The easier it is for us the faster |
| 29 |
it'll go. |
| 30 |
|
| 31 |
6) Press "Commit" |
| 32 |
|
| 33 |
7) You will now come to a new page. Here press "Attach a file to this |
| 34 |
bug". Choose "Plain/Text" as content type. Upload your ebuild/patch. |
| 35 |
|
| 36 |
!! Next is optional !! |
| 37 |
8) If you are commiting several bugs that depend on each other it makes |
| 38 |
it easier for us if you mark them as dependant in the bugzilla. |
| 39 |
Press the link "Back to To BUG #..." and you can write the bug# of |
| 40 |
the other ebuilds it depends on. |
| 41 |
|
| 42 |
Regards, |
| 43 |
Mikael Hallendal |
| 44 |
|
| 45 |
-- |
| 46 |
Mikael Hallendal |
| 47 |
Gentoo Linux Developer, Desktop Team Leader |
| 48 |
CodeFactory AB, Stockholm, Sweden |
Archives