jkt 08/01/31 14:31:41 Modified: bugzilla-howto.xml Log: s/digest/Manifest/ and related fixes
Revision Changes Path 1.11 xml/htdocs/doc/en/bugzilla-howto.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.11&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.11&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?r1=1.10&r2=1.11 Index: bugzilla-howto.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- bugzilla-howto.xml 1 Apr 2007 10:35:45 -0000 1.10 +++ bugzilla-howto.xml 31 Jan 2008 14:31:41 -0000 1.11 @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.10 2007/04/01 10:35:45 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.11 2008/01/31 14:31:41 jkt Exp $ --> <guide link="/doc/en/bugzilla-howto.xml"> <title>Gentoo Bug Reporting Guide</title> @@ -20,8 +20,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>1.9</version> -<date>2007-04-01</date> +<version>1.10</version> +<date>2008-01-31</date> <chapter> <title>Introduction</title> @@ -1343,7 +1343,7 @@ Now we'll want to create the appropriate directories to put our test ebuild files in. In this case, we're supposed to put them in sys-apps/foobar2. You'll notice that the second comment asks for a files directory for the patch. The -files directory holds the digests (md5sums of files for a particular version of +files directory holds the Manifest files (md5sums of files for a particular version of a package) and any other required files that aren't included with the standard source archive (patches, init.d scripts, etc). This is a subdir in the package directory called files. Go ahead and create these directories: @@ -1373,19 +1373,13 @@ <p> The process to create an ebuild that can be used by emerge is fairly simple. You -must create a Manifest and a digest file for the ebuild. This can be done with +must create a Manifest file for the ebuild. This can be done with the ebuild command. Run it as shown. </p> -<pre caption="Creating the Manifest and digest files"> -# <i>ebuild foobar2-1.0.ebuild digest</i> ->>> Generating digest file... -<<< foobar2-1.0.tar.bz2 ->>> Generating manifest file... -<<< foobar2-1.0.ebuild -<<< files/digest-foobar2-1.0 -<<< files/foobar2-1.0-Makefile.patch ->>> Computed message digests. +<pre caption="Creating the Manifest file"> +# <i>ebuild foobar2-1.0.ebuild manifest</i> +>>> Creating Manifest for /usr/local/portage/sys-apps/foobar2 </pre> <p> -- [email protected] mailing list
