| 1 |
jkt 08/01/31 14:31:41 |
| 2 |
|
| 3 |
Modified: bugzilla-howto.xml |
| 4 |
Log: |
| 5 |
s/digest/Manifest/ and related fixes |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.11 xml/htdocs/doc/en/bugzilla-howto.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.11&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.11&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?r1=1.10&r2=1.11 |
| 13 |
|
| 14 |
Index: bugzilla-howto.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v |
| 17 |
retrieving revision 1.10 |
| 18 |
retrieving revision 1.11 |
| 19 |
diff -u -r1.10 -r1.11 |
| 20 |
--- bugzilla-howto.xml 1 Apr 2007 10:35:45 -0000 1.10 |
| 21 |
+++ bugzilla-howto.xml 31 Jan 2008 14:31:41 -0000 1.11 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.10 2007/04/01 10:35:45 nightmorph Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.11 2008/01/31 14:31:41 jkt Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/en/bugzilla-howto.xml"> |
| 29 |
<title>Gentoo Bug Reporting Guide</title> |
| 30 |
@@ -20,8 +20,8 @@ |
| 31 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 32 |
<license/> |
| 33 |
|
| 34 |
-<version>1.9</version> |
| 35 |
-<date>2007-04-01</date> |
| 36 |
+<version>1.10</version> |
| 37 |
+<date>2008-01-31</date> |
| 38 |
|
| 39 |
<chapter> |
| 40 |
<title>Introduction</title> |
| 41 |
@@ -1343,7 +1343,7 @@ |
| 42 |
Now we'll want to create the appropriate directories to put our test ebuild |
| 43 |
files in. In this case, we're supposed to put them in sys-apps/foobar2. You'll |
| 44 |
notice that the second comment asks for a files directory for the patch. The |
| 45 |
-files directory holds the digests (md5sums of files for a particular version of |
| 46 |
+files directory holds the Manifest files (md5sums of files for a particular version of |
| 47 |
a package) and any other required files that aren't included with the standard |
| 48 |
source archive (patches, init.d scripts, etc). This is a subdir in the package |
| 49 |
directory called files. Go ahead and create these directories: |
| 50 |
@@ -1373,19 +1373,13 @@ |
| 51 |
|
| 52 |
<p> |
| 53 |
The process to create an ebuild that can be used by emerge is fairly simple. You |
| 54 |
-must create a Manifest and a digest file for the ebuild. This can be done with |
| 55 |
+must create a Manifest file for the ebuild. This can be done with |
| 56 |
the ebuild command. Run it as shown. |
| 57 |
</p> |
| 58 |
|
| 59 |
-<pre caption="Creating the Manifest and digest files"> |
| 60 |
-# <i>ebuild foobar2-1.0.ebuild digest</i> |
| 61 |
->>> Generating digest file... |
| 62 |
-<<< foobar2-1.0.tar.bz2 |
| 63 |
->>> Generating manifest file... |
| 64 |
-<<< foobar2-1.0.ebuild |
| 65 |
-<<< files/digest-foobar2-1.0 |
| 66 |
-<<< files/foobar2-1.0-Makefile.patch |
| 67 |
->>> Computed message digests. |
| 68 |
+<pre caption="Creating the Manifest file"> |
| 69 |
+# <i>ebuild foobar2-1.0.ebuild manifest</i> |
| 70 |
+>>> Creating Manifest for /usr/local/portage/sys-apps/foobar2 |
| 71 |
</pre> |
| 72 |
|
| 73 |
<p> |
| 74 |
|
| 75 |
|
| 76 |
|
| 77 |
-- |
| 78 |
gentoo-doc-cvs@l.g.o mailing list |
Archives