Gentoo Archives: gentoo-doc-cvs

From: Jan Kundrat <jkt@××××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: gentoo-ppc-faq.xml
Date: Thu, 31 Jan 2008 14:34:25
Message-Id: E1JKaUH-0003WB-PI@stork.gentoo.org
1 jkt 08/01/31 14:33:57
2
3 Modified: gentoo-ppc-faq.xml
4 Log:
5 s/digest/manifest/ and stuff like that
6
7 Revision Changes Path
8 1.67 xml/htdocs/doc/en/gentoo-ppc-faq.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml?rev=1.67&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml?rev=1.67&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml?r1=1.66&r2=1.67
13
14 Index: gentoo-ppc-faq.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml,v
17 retrieving revision 1.66
18 retrieving revision 1.67
19 diff -u -r1.66 -r1.67
20 --- gentoo-ppc-faq.xml 18 Jan 2008 23:37:28 -0000 1.66
21 +++ gentoo-ppc-faq.xml 31 Jan 2008 14:33:57 -0000 1.67
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/gentoo-ppc-faq.xml,v 1.66 2008/01/18 23:37:28 nightmorph Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml,v 1.67 2008/01/31 14:33:57 jkt Exp $ -->
27
28 <guide link="/doc/en/gentoo-ppc-faq.xml">
29 <title>Gentoo Linux/PowerPC Frequently Asked Questions</title>
30 @@ -27,8 +27,8 @@
31 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
32 <license/>
33
34 -<version>1.38</version>
35 -<date>2008-01-18</date>
36 +<version>1.39</version>
37 +<date>2008-01-31</date>
38
39 <faqindex>
40 <title>Questions</title>
41 @@ -827,13 +827,13 @@
42 <p>
43 If your package hasn't yet been tested on PPC, you'll need to first mark the
44 ebuild with the ppc keyword. This is done using the ekeyword tool which is part
45 -of the gentoolkit-dev package. To mark the ebuild ppc and re-digest it to
46 -reflect the changes:
47 +of the gentoolkit-dev package. To mark the ebuild ppc and regenerate the
48 +manifest file so that it reflects the changes:
49 </p>
50
51 <pre caption="Adding the ppc keyword to app-foo/bar">
52 # <i>ekeyword ppc /usr/portage/app-foo/bar/bar-1.0.ebuild</i>
53 -# <i>ebuild /usr/portage/app-foo/bar/bar-1.0.ebuild digest</i>
54 +# <i>ebuild /usr/portage/app-foo/bar/bar-1.0.ebuild manifest</i>
55 </pre>
56
57 <p>
58
59
60
61 --
62 gentoo-doc-cvs@l.g.o mailing list