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 @@ <?xml version="1.0" encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ebuild-submit.xml,v 1.12 2005/10/24 13:29:47 flammie Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ebuild-submit.xml,v 1.13 2007/07/16 03:04:29 nightmorph Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link = "/doc/en/ebuild-submit.xml"> <title>Contributing Ebuilds</title> + <author title="Author"> <mail link="[EMAIL PROTECTED]">Matt Butcher</mail> </author> @@ -23,11 +24,10 @@ <body> <p> -Point your web browser to <uri>http://bugs.gentoo.org</uri>. 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 <uri>http://bugs.gentoo.org</uri>. 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. </p> </body> @@ -59,29 +59,27 @@ <body> <p> -At the bottom of the main page or login page, there is a -yellow box. Choose the <c>New - Expert</c> link. Or, you can just go -to the URL <uri>http://bugs.gentoo.org/enter_bug.cgi</uri>. -Either will bring you to the <c>Enter Bug</c> page. +At the bottom of the main page or login page, there is a yellow box. Choose the +<c>New - Expert</c> link. Or, you can just go to the URL +<uri>http://bugs.gentoo.org/enter_bug.cgi</uri>. Either will bring you to the +<c>Enter Bug</c> page. </p> <note> -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. </note> <p> -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 <c>Gentoo Linux</c>. +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 <c>Gentoo Linux</c>. </p> <p> -Clicking on the <c>Gentoo Linux</c> product should bring up -a new bug entry form. +Clicking on the <c>Gentoo Linux</c> product should bring up a new bug entry +form. </p> </body> @@ -91,23 +89,21 @@ <body> <p> -The first field on the form is <c>version</c>. If you know -which version your package belongs in, set it here. Otherwise, -select <c>unspecified</c>. Next, set the component. All ebuild -scripts are of the component type <c>Ebuilds</c>. +The first field on the form is <c>version</c>. If you know which version your +package belongs in, set it here. Otherwise, select <c>unspecified</c>. Next, set +the component. All ebuild scripts are of the component type <c>Ebuilds</c>. </p> <impo> -Ebuilds should <e>always</e> be of component type -<c>Ebuild</c>. Categories such as <c>GNOME</c>, -<c>Libraries</c>, and <c>Server</c> may look like they apply to -your ebuild, but they are used for filing bugs against packages, -not submitting ebuilds. +Ebuilds should <e>always</e> be of component type <c>Ebuild</c>. Categories such +as <c>GNOME</c>, <c>Libraries</c>, and <c>Server</c> may look like they apply to +your ebuild, but they are used for filing bugs against packages, not submitting +ebuilds. </impo> <p> -The categories <c>Platform</c>, <c>OS</c>, and -<c>Priority</c> do not need to be set for ebuilds. +The categories <c>Platform</c>, <c>OS</c>, and <c>Priority</c> do not need to be +set for ebuilds. </p> <p> @@ -115,21 +111,20 @@ </p> <p> -Leave the <c>Assigned To</c> field blank. If you haven't changed -Bugzilla's mail settings, you, as a reporter, will automatically -receive email on bug updates. +Leave the <c>Assigned To</c> field blank. If you haven't changed Bugzilla's mail +settings, you, as a reporter, will automatically receive email on bug updates. </p> <p> -Fill in the <c>Summary</c> 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: <c>foo-bar-x.y.z.ebuild -(New Package)</c> or <c>foo-x.y.z.ebuild (Update)</c>. +Fill in the <c>Summary</c> 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: <c>foo-bar-x.y.z.ebuild (New Package)</c> or +<c>foo-x.y.z.ebuild (Update)</c>. </p> <p> -The <c>Description</c> field should be filled in as completely -as possible. Here's an example from Bug Number 7: +The <c>Description</c> field should be filled in as completely as possible. +Here's an example from Bug Number 7: </p> <pre caption="Example description"> @@ -161,29 +156,29 @@ <body> <p> -After clicking <c>submit</c> on the <c>Enter Bug</c> page, you -will go to the <c>Posting Bug</c> page. Take note of the bug number. +After clicking <c>submit</c> on the <c>Enter Bug</c> page, you will go to the +<c>Posting Bug</c> page. Take note of the bug number. </p> <p> -Toward the bottom of this page, there is a link to <c>Create a new +Toward the bottom of this page, there is a link to <c>Create a new attachment</c>. Click on this link. </p> <p> -Select the file using the text entry box or the <c>Browse</c> dialog. -In the <c>Description</c> field, type the name of the ebuild file, much -the same as you did in the <c>Summary</c> section of the last page. +Select the file using the text entry box or the <c>Browse</c> dialog. In the +<c>Description</c> field, type the name of the ebuild file, much the same as you +did in the <c>Summary</c> section of the last page. </p> <p> -Make sure that the content type is set to "text/plain", and that the -radiobutton for <c>select from list</c> is marked. +Make sure that the content type is set to "text/plain", and that the radiobutton +for <c>select from list</c> is marked. </p> <p> -There are no other required fields on this form. Click <c>Submit</c> -and you are done! +There are no other required fields on this form. Click <c>Submit</c> and you are +done! </p> </body> @@ -197,10 +192,10 @@ <body> <p> -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. </p> </body> -- [EMAIL PROTECTED] mailing list
