| 1 |
flameeyes 08/01/25 18:12:27 |
| 2 |
|
| 3 |
Modified: automagic.xml |
| 4 |
Log: |
| 5 |
Fix a few grammar mistakes. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.3 xml/htdocs/proj/en/qa/automagic.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/automagic.xml?rev=1.3&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/automagic.xml?rev=1.3&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/automagic.xml?r1=1.2&r2=1.3 |
| 13 |
|
| 14 |
Index: automagic.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/automagic.xml,v |
| 17 |
retrieving revision 1.2 |
| 18 |
retrieving revision 1.3 |
| 19 |
diff -u -r1.2 -r1.3 |
| 20 |
--- automagic.xml 30 Jan 2006 05:52:05 -0000 1.2 |
| 21 |
+++ automagic.xml 25 Jan 2008 18:12:26 -0000 1.3 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "http://www.gentoo.org/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/automagic.xml,v 1.2 2006/01/30 05:52:05 flameeyes Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/automagic.xml,v 1.3 2008/01/25 18:12:26 flameeyes Exp $ --> |
| 27 |
|
| 28 |
<guide link="/proj/en/qa/automagic.xml" lang="en"> |
| 29 |
<title>Automagic dependencies, what they are and how to fix them</title> |
| 30 |
@@ -29,7 +29,7 @@ |
| 31 |
<body> |
| 32 |
|
| 33 |
<p> |
| 34 |
-The so-called <e>automagic dependecies</e> are shallow dependencies of a |
| 35 |
+The so-called <e>automagic dependencies</e> are shallow dependencies of a |
| 36 |
software recognized at build or runtime and changes the way the software works. |
| 37 |
The name <e>automagic</e> is a pun referred to the use of GNU autotools, that |
| 38 |
produces most of the cases of <e>automagic dependencies</e>. |
| 39 |
@@ -101,7 +101,7 @@ |
| 40 |
When a package has automagic dependencies there are only two things that can |
| 41 |
be done: the first is to state the dependency as mandatory, no matter what the |
| 42 |
users put in their USE variable, but that might mean that some support that |
| 43 |
-people don't want is always enable and its dependencies pulle din; the other |
| 44 |
+people don't want is always enable and its dependencies pulled in; the other |
| 45 |
is to fix the build system to be able to disable at build time the dependency |
| 46 |
also if it's present on the system. |
| 47 |
</p> |
| 48 |
@@ -150,7 +150,7 @@ |
| 49 |
corresponding variable before doing the test. It's useful to know that the first |
| 50 |
parameter passed to the above macro actually names a variable that gets loaded |
| 51 |
by <c>autoconf</c> without having to add the extra parameters for action to |
| 52 |
-execute when the parameter is present and when it's not, the variale is named |
| 53 |
+execute when the parameter is present and when it's not, the variable is named |
| 54 |
<path>$enable_foo</path> or <path>$with_bar</path>, depending on which of the |
| 55 |
two macros are called. |
| 56 |
</p> |
| 57 |
@@ -183,7 +183,7 @@ |
| 58 |
When the parameter is present but it's not honoured, it might be simple as well |
| 59 |
as complex to fix the dependency. It might just be a test that's not properly |
| 60 |
written, so it has to be changed in something alike to the tests above, or it |
| 61 |
-might be a complete screwup in calls of <b>AC_ARG_WITH</b> macros. In those |
| 62 |
+might be a complete screw-up in calls of <b>AC_ARG_WITH</b> macros. In those |
| 63 |
cases, it's better to check the code carefully and contact upstream if a screw |
| 64 |
up seems likely. |
| 65 |
</p> |
| 66 |
|
| 67 |
|
| 68 |
|
| 69 |
-- |
| 70 |
gentoo-commits@l.g.o mailing list |
Archives