1 |
fauli 10/01/08 09:49:01 |
2 |
|
3 |
Modified: arch-testers-faq.xml |
4 |
Log: |
5 |
AT FAQ: Some words on dependencies |
6 |
|
7 |
Revision Changes Path |
8 |
1.17 xml/htdocs/proj/en/base/x86/arch-testers-faq.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml?rev=1.17&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml?rev=1.17&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml?r1=1.16&r2=1.17 |
13 |
|
14 |
Index: arch-testers-faq.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml,v |
17 |
retrieving revision 1.16 |
18 |
retrieving revision 1.17 |
19 |
diff -u -r1.16 -r1.17 |
20 |
--- arch-testers-faq.xml 8 Jan 2010 09:36:25 -0000 1.16 |
21 |
+++ arch-testers-faq.xml 8 Jan 2010 09:49:01 -0000 1.17 |
22 |
@@ -2,7 +2,7 @@ |
23 |
|
24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
25 |
|
26 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml,v 1.16 2010/01/08 09:36:25 fauli Exp $ --> |
27 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml,v 1.17 2010/01/08 09:49:01 fauli Exp $ --> |
28 |
|
29 |
<guide link="/proj/en/base/x86/arch-testers-faq.xml"> |
30 |
<title>Gentoo x86 Arch Tester's FAQ</title> |
31 |
@@ -320,6 +320,14 @@ |
32 |
security bugs and keywording requests have absolute priority. |
33 |
</li> |
34 |
<li> |
35 |
+ Normally, all needed packages are listed in the request, but |
36 |
+ sometimes, dependencies are forgotten. This is usually no |
37 |
+ problem for most things, but you should include it in your report |
38 |
+ nonetheless. To automatically add all needed packages to the |
39 |
+ <c>package.keywords</c> file, you may use <uri |
40 |
+ link="http://packages.gentoo.org/package/app-portage/gatt">app-portage/gatt</uri>. |
41 |
+ </li> |
42 |
+ <li> |
43 |
After merging the package with various USE flag combinations, run |
44 |
it and ensure that basic functionality works. If the package is a |
45 |
library, emerge a couple of packages (best: all that depend on it |