| 1 |
shadow 08/02/01 10:55:54 |
| 2 |
|
| 3 |
Modified: gentoo-ppc-faq.xml |
| 4 |
Log: |
| 5 |
sync to 1.67 |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.29 xml/htdocs/doc/pl/gentoo-ppc-faq.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/gentoo-ppc-faq.xml?rev=1.29&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/gentoo-ppc-faq.xml?rev=1.29&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/gentoo-ppc-faq.xml?r1=1.28&r2=1.29 |
| 13 |
|
| 14 |
Index: gentoo-ppc-faq.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/pl/gentoo-ppc-faq.xml,v |
| 17 |
retrieving revision 1.28 |
| 18 |
retrieving revision 1.29 |
| 19 |
diff -u -r1.28 -r1.29 |
| 20 |
--- gentoo-ppc-faq.xml 21 Jan 2008 11:47:51 -0000 1.28 |
| 21 |
+++ gentoo-ppc-faq.xml 1 Feb 2008 10:55:53 -0000 1.29 |
| 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/pl/gentoo-ppc-faq.xml,v 1.28 2008/01/21 11:47:51 rane Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/pl/gentoo-ppc-faq.xml,v 1.29 2008/02/01 10:55:53 shadow Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/pl/gentoo-ppc-faq.xml" lang="pl"> |
| 29 |
<title>Gentoo/PPC, często zadawane pytania</title> |
| 30 |
@@ -29,8 +29,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>Pytania</title> |
| 41 |
@@ -848,12 +848,12 @@ |
| 42 |
Jeśli pakiet nie został przetestowany na architekturze PPC, należy dodać słowo |
| 43 |
kluczowe ppc do ebuildu. Wykonamy to za pomocą narzędzia ekeyword, które jest |
| 44 |
częścią pakietu gentoolkit-dev. Dodawanie słowa kluczowego do ebuildu oraz |
| 45 |
-sprawdzenie jego sum md5 w celu uwzględnienia przez portage zmian: |
| 46 |
+ponowne wygenerowanie pliku Manifest z sumami kontrolnymi: |
| 47 |
</p> |
| 48 |
|
| 49 |
<pre caption="Dodawanie słowa kluczowego ppc do app-foo/bar"> |
| 50 |
# <i>ekeyword ppc /usr/portage/app-foo/bar/bar-1.0.ebuild</i> |
| 51 |
-# <i>ebuild /usr/portage/app-foo/bar/bar-1.0.ebuild digest</i> |
| 52 |
+# <i>ebuild /usr/portage/app-foo/bar/bar-1.0.ebuild manifest</i> |
| 53 |
</pre> |
| 54 |
|
| 55 |
<p> |
| 56 |
|
| 57 |
|
| 58 |
|
| 59 |
-- |
| 60 |
gentoo-commits@l.g.o mailing list |
Archives