Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 29 Details for
Bug 70
Document for Ebuild submissions via Bugzilla
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
Guide for contributing ebuilds via mozilla
ebuild_contribs.xml (text/plain), 4.93 KB, created by
Matt Butcher
on 2002-01-07 13:22:46 UTC
(
hide
)
Description:
Guide for contributing ebuilds via mozilla
Filename:
MIME Type:
Creator:
Matt Butcher
Created:
2002-01-07 13:22:46 UTC
Size:
4.93 KB
patch
obsolete
><?xml version="1.0"?> ><guide> > <title>Contributing Ebuilds</title> > <author> > <mail link="mbutcher@frii.com">Matt Butcher</mail> > </author> > <abstract> > This guide explains how to submit ebuild packages through the Bugzilla > tracking system. > </abstract> > > <version>1.0</version> > <date>7 Jan, 2002</date> > > <chapter> > <title>Getting Started</title> > <section> > <title>Create A Bugzilla Account</title> > <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.</p> > </body> > </section> > </chapter> > <chapter> > <title>Submitting an ebuild</title> > <section> > <title>Create a new bug</title> > <body> > <p>At the bottom of the main page or login page, there is a > yellow box. Choose the <c>New</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. > </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></p> > > <p>Clicking on the <c>Gentoo Linux</c> product should bring up > a new bug entry form.</p> > </body> > </section> > <section> > <title>Completing the bug form</title> > <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></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. > </impo> > > <p>The categories <c>Platform</c>, <c>OS</c>, and > <c>Priority</c> do not need to be set for ebuilds.</p> > > <p>The <c>Severity</c> field should be set to > <c>enhancement</c></p> > > <p>Leave the <c>Assigned To</c> field blank, but if you'd like > to track the status of your ebuild, enter your email in the > <c>CC</c> field.</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></p> > > <p>The <c>Description</c> field should be filled in as completely > as possible. Here's an example from Bug Number 7:</p> > <pre> > Hi! > >Please find attached gramps.tar.gz containing gramps-0.7.0.ebuild and a >patch so that it will compile against python-2.2 > >gramps is the Genealogical Research and Analysis Management Programming >System. It is a very cool gnome/python app. If you are in the US, you >can head over to >http://www.familysearch.com/ >and you can probably find a GEDCOM file for your family tree to import >into gramps. (Mormons sure do like geneaology) > >I suggest app-misc/gramps Also, this ebuild depend on Imaging and ReportLab >previously submitted > >tod > > </pre> > <p>Once the summary is complete, click <c>Submit</c>.</p> > </body> > </section> > <section> > <title>Attaching the Ebuild Script</title> > <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.</p> > > <p>Toward the bottom of this page, there is a link to <c>Attach a file to > this bug</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.</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.</p> > > <p>There are no other required fields on this form. Click <c>Submit</c> > and you are done!</p> > </body> > </section> > </chapter> > <chapter> > <title>Multiple Ebuilds</title> > <section> > <title>Dependancies</title> > <body> > <p>In cases where you might submit multiple ebuilds, and some of them > depend on others, it is very helpful if these dependancies are noted. > Viewing the bug again should allow you to enter another note. Please add > dependancy information here.</p> > </body> > </section> > </chapter> ></guide>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 70
: 29