/[gentoo]/xml/htdocs/doc/en/bugzilla-howto.xml
Gentoo

Diff of /xml/htdocs/doc/en/bugzilla-howto.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.9 Revision 1.12
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.9 2007/02/14 21:30:15 nightmorph Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.12 2008/02/01 19:30:40 jkt Exp $ -->
4 4
5<guide link="/doc/en/bugzilla-howto.xml"> 5<guide link="/doc/en/bugzilla-howto.xml">
6<title>Gentoo Bug Reporting Guide</title> 6<title>Gentoo Bug Reporting Guide</title>
7 7
8<author title="Author"> 8<author title="Author">
18 18
19<!-- The content of this document is licensed under the CC-BY-SA license --> 19<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 20<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
21<license/> 21<license/>
22 22
23<version>1.8</version> 23<version>1.11</version>
24<date>2007-02-14</date> 24<date>2008-01-31</date>
25 25
26<chapter> 26<chapter>
27<title>Introduction</title> 27<title>Introduction</title>
28<section> 28<section>
29<title>Preface</title> 29<title>Preface</title>
846 Build Identifier is basically the User Agent of the browser that is being 846 Build Identifier is basically the User Agent of the browser that is being
847 used to report the bugs (for logging purposes). You can just leave this as 847 used to report the bugs (for logging purposes). You can just leave this as
848 is. 848 is.
849 </li> 849 </li>
850 <li> 850 <li>
851 URL is optional and is used to point to errors on a site someplace 851 URL is optional and is used to point to relevant information on another site
852 (pastebin, etc.). However, doing it inside the bug allows the developers be 852 (upstream bugzilla, release notes on package homepage etc.). You should
853 able to reference to it at any time and is preferred. 853 never use URL to point to pastebins for error messages, logs, <c>emerge
854 --info</c> output, screenshots or similar information. Instead, these should
855 always be attached to the bug.
854 </li> 856 </li>
855 <li> 857 <li>
856 In the Summary, you should put the package category, name, and number. 858 In the Summary, you should put the package category, name, and number.
857 </li> 859 </li>
858</ul> 860</ul>
1338</pre> 1340</pre>
1339 1341
1340<p> 1342<p>
1341Now we'll want to create the appropriate directories to put our test ebuild 1343Now we'll want to create the appropriate directories to put our test ebuild
1342files in. In this case, we're supposed to put them in sys-apps/foobar2. You'll 1344files in. In this case, we're supposed to put them in sys-apps/foobar2. You'll
1343notice that the second comment asks for a files directory for the patch. The 1345notice that the second comment asks for a <path>files</path> directory for the
1344files directory holds the digests (md5sums of files for a particular version of 1346patch. This directory holds other required files that aren't included with
1345a package) and any other required files that aren't included with the standard
1346source archive (patches, init.d scripts, etc). This is a subdir in the package 1347the standard source archive (patches, init.d scripts, etc). This is a subdir in
1347directory called files. Go ahead and create these directories: 1348the package directory called <path>files</path>. Go ahead and create these
1349directories:
1348</p> 1350</p>
1349 1351
1350<pre caption="Setting Up The Category And Package Directories"> 1352<pre caption="Setting Up The Category And Package Directories">
1351# <i>mkdir -p /usr/local/portage/sys-apps/foobar2/files</i> 1353# <i>mkdir -p /usr/local/portage/sys-apps/foobar2/files</i>
1352</pre> 1354</pre>
1369<title>Testing The ebuild</title> 1371<title>Testing The ebuild</title>
1370<body> 1372<body>
1371 1373
1372<p> 1374<p>
1373The process to create an ebuild that can be used by emerge is fairly simple. You 1375The process to create an ebuild that can be used by emerge is fairly simple. You
1374must create a Manifest and a digest file for the ebuild. This can be done with 1376must create a Manifest file for the ebuild. This can be done with
1375the ebuild command. Run it as shown. 1377the ebuild command. Run it as shown.
1376</p> 1378</p>
1377 1379
1378<pre caption="Creating the Manifest and digest files"> 1380<pre caption="Creating the Manifest file">
1379# <i>ebuild foobar2-1.0.ebuild digest</i> 1381# <i>ebuild foobar2-1.0.ebuild manifest</i>
1380&gt;&gt;&gt; Generating digest file... 1382&gt;&gt;&gt; Creating Manifest for /usr/local/portage/sys-apps/foobar2
1381&lt;&lt;&lt; foobar2-1.0.tar.bz2
1382&gt;&gt;&gt; Generating manifest file...
1383&lt;&lt;&lt; foobar2-1.0.ebuild
1384&lt;&lt;&lt; files/digest-foobar2-1.0
1385&lt;&lt;&lt; files/foobar2-1.0-Makefile.patch
1386&gt;&gt;&gt; Computed message digests.
1387</pre> 1383</pre>
1388 1384
1389<p> 1385<p>
1390Now let's test to see if it works as it should. 1386Now let's test to see if it works as it should.
1391</p> 1387</p>

Legend:
Removed from v.1.9  
changed lines
  Added in v.1.12

  ViewVC Help
Powered by ViewVC 1.1.20