From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1IAGt4-00016q-7S for garchives@archives.gentoo.org; Mon, 16 Jul 2007 03:04:39 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l6G34TV3018951; Mon, 16 Jul 2007 03:04:29 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l6G34Ss6018945 for ; Mon, 16 Jul 2007 03:04:28 GMT Received: from stork.gentoo.org (stork.gentoo.org [64.127.104.133]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id D9F5C652A4 for ; Mon, 16 Jul 2007 03:04:27 +0000 (UTC) Received: from nightmorph by stork.gentoo.org with local (Exim 4.60) (envelope-from ) id 1IAGsv-0004lP-V9 for gentoo-doc-cvs@lists.gentoo.org; Mon, 16 Jul 2007 03:04:30 +0000 To: gentoo-doc-cvs@lists.gentoo.org Subject: [gentoo-doc-cvs] cvs commit: ebuild-submit.xml Message-Id: From: Josh Saddler Date: Mon, 16 Jul 2007 03:04:29 +0000 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-doc-cvs@gentoo.org Reply-to: docs-team@lists.gentoo.org X-Archives-Salt: 580c933a-755a-48b5-9156-84569d2aef67 X-Archives-Hash: e540ef10b4b30f03570e1be57697087a nightmorph 07/07/16 03:04:29 Modified: ebuild-submit.xml Log: guidexml coding style fixes, no content change Revision Changes Path 1.13 xml/htdocs/doc/en/ebuild-submit.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/ebuild-submit.xml?rev=1.13&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/ebuild-submit.xml?rev=1.13&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/ebuild-submit.xml?r1=1.12&r2=1.13 Index: ebuild-submit.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/ebuild-submit.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- ebuild-submit.xml 24 Oct 2005 13:29:47 -0000 1.12 +++ ebuild-submit.xml 16 Jul 2007 03:04:29 -0000 1.13 @@ -1,9 +1,10 @@ - + Contributing Ebuilds + Matt Butcher @@ -23,11 +24,10 @@

-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. +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.

@@ -59,29 +59,27 @@

-At the bottom of the main page or login page, there is a -yellow box. Choose the New - Expert link. Or, you can just go -to the URL http://bugs.gentoo.org/enter_bug.cgi. -Either will bring you to the Enter Bug page. +At the bottom of the main page or login page, there is a yellow box. Choose the +New - Expert link. Or, you can just go to the URL +http://bugs.gentoo.org/enter_bug.cgi. Either will bring you to the +Enter Bug page.

-In the Bugzilla system, all entries are bugs. That includes -newly submitted ebuilds. Each bug is assigned a tracking id. -Take note of the ID, especially if you have other ebuilds that -depend on this package. +In the Bugzilla system, all entries are bugs. That includes newly submitted +ebuilds. Each bug is assigned a tracking id. Take note of the ID, especially if +you have other ebuilds that depend on this package.

-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 Gentoo Linux. +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 Gentoo Linux.

-Clicking on the Gentoo Linux product should bring up -a new bug entry form. +Clicking on the Gentoo Linux product should bring up a new bug entry +form.

@@ -91,23 +89,21 @@

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

-Ebuilds should always be of component type -Ebuild. Categories such as GNOME, -Libraries, and Server may look like they apply to -your ebuild, but they are used for filing bugs against packages, -not submitting ebuilds. +Ebuilds should always be of component type Ebuild. Categories such +as GNOME, Libraries, and Server may look like they apply to +your ebuild, but they are used for filing bugs against packages, not submitting +ebuilds.

-The categories Platform, OS, and -Priority do not need to be set for ebuilds. +The categories Platform, OS, and Priority do not need to be +set for ebuilds.

@@ -115,21 +111,20 @@

-Leave the Assigned To field blank. If you haven't changed -Bugzilla's mail settings, you, as a reporter, will automatically -receive email on bug updates. +Leave the Assigned To 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 Summary 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: foo-bar-x.y.z.ebuild -(New Package) or foo-x.y.z.ebuild (Update). +Fill in the Summary 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: foo-bar-x.y.z.ebuild (New Package) or +foo-x.y.z.ebuild (Update).

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

@@ -161,29 +156,29 @@
 
 
 

-After clicking submit on the Enter Bug page, you 
-will go to the Posting Bug page. Take note of the bug number.
+After clicking submit on the Enter Bug page, you will go to the
+Posting Bug page. Take note of the bug number.
 

 
 

-Toward the bottom of this page, there is a link to Create a new 
+Toward the bottom of this page, there is a link to Create a new
 attachment. Click on this link.
 

 
 

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

 
 

-Make sure that the content type is set to "text/plain", and that the
-radiobutton for select from list is marked.
+Make sure that the content type is set to "text/plain", and that the radiobutton
+for select from list is marked.
 

 
 

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

 
 
@@ -197,10 +192,10 @@
 
 
 

-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.
+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.
 

 
 



-- 
gentoo-doc-cvs@gentoo.org mailing list