| 1 |
swift 08/05/20 18:44:03 |
| 2 |
|
| 3 |
Modified: gentoolkit.xml |
| 4 |
Log: |
| 5 |
Coding style |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.31 xml/htdocs/doc/en/gentoolkit.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoolkit.xml?rev=1.31&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoolkit.xml?rev=1.31&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoolkit.xml?r1=1.30&r2=1.31 |
| 13 |
|
| 14 |
Index: gentoolkit.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v |
| 17 |
retrieving revision 1.30 |
| 18 |
retrieving revision 1.31 |
| 19 |
diff -u -r1.30 -r1.31 |
| 20 |
--- gentoolkit.xml 26 Jun 2007 04:14:39 -0000 1.30 |
| 21 |
+++ gentoolkit.xml 20 May 2008 18:44:03 -0000 1.31 |
| 22 |
@@ -1,5 +1,5 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v 1.30 2007/06/26 04:14:39 nightmorph Exp $ --> |
| 25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v 1.31 2008/05/20 18:44:03 swift Exp $ --> |
| 26 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 27 |
|
| 28 |
<guide link="/doc/en/gentoolkit.xml"> |
| 29 |
@@ -59,16 +59,16 @@ |
| 30 |
As of now, there are two versions of gentoolkit: <c>app-portage/gentoolkit</c> |
| 31 |
and <c>app-portage/gentoolkit-dev</c>. While the former contains administration |
| 32 |
scripts, the latter contains scripts specific to help development on Gentoo. |
| 33 |
-If you are a developer, you can have your scripts included into |
| 34 |
-<c>gentoolkit-dev</c> by contacting the Gentoolkit maintainer. This document |
| 35 |
-discusses gentoolkit only. |
| 36 |
+If you are a developer, you can have your scripts included into |
| 37 |
+<c>gentoolkit-dev</c> by contacting the Gentoolkit maintainer. This document |
| 38 |
+discusses gentoolkit only. |
| 39 |
</note> |
| 40 |
|
| 41 |
<p> |
| 42 |
Gentoolkit contains a whole bunch of useful tools to help manage your packages |
| 43 |
-and keep track of what is going on in your system. Most users -- particularly |
| 44 |
-those who update systems often -- will benefit from having gentoolkit |
| 45 |
-installed. |
| 46 |
+and keep track of what is going on in your system. Most users |
| 47 |
+-- particularly those who update systems often -- will benefit from |
| 48 |
+having gentoolkit installed. |
| 49 |
</p> |
| 50 |
|
| 51 |
</body> |
| 52 |
@@ -138,7 +138,7 @@ |
| 53 |
<body> |
| 54 |
|
| 55 |
<p> |
| 56 |
-<c>equery</c> also provides the functionality of finding the package that a |
| 57 |
+<c>equery</c> also provides the functionality of finding the package that a |
| 58 |
file came from, using <c>belongs</c> command (or just <c>b</c>). |
| 59 |
</p> |
| 60 |
|
| 61 |
@@ -149,8 +149,8 @@ |
| 62 |
</pre> |
| 63 |
|
| 64 |
<p> |
| 65 |
-By using the <c>-f</c> option, you may search for packages with files |
| 66 |
-matching any regular expression. The <c>-e</c> option is useful for |
| 67 |
+By using the <c>-f</c> option, you may search for packages with files |
| 68 |
+matching any regular expression. The <c>-e</c> option is useful for |
| 69 |
terminating your search immediately when a match is found. |
| 70 |
</p> |
| 71 |
|
| 72 |
@@ -161,8 +161,8 @@ |
| 73 |
<body> |
| 74 |
|
| 75 |
<p> |
| 76 |
-Sometimes it is useful to check a package's integrity. <c>equery</c> can |
| 77 |
-verify md5 sums as well as timestamps to indicate when a package might |
| 78 |
+Sometimes it is useful to check a package's integrity. <c>equery</c> can |
| 79 |
+verify md5 sums as well as timestamps to indicate when a package might |
| 80 |
have been corrupted, replaced, or removed. |
| 81 |
</p> |
| 82 |
|
| 83 |
@@ -185,7 +185,7 @@ |
| 84 |
|
| 85 |
<p> |
| 86 |
<c>equery</c> is able to list all direct dependencies matching a package. |
| 87 |
-The function we should use to do this is <c>depends</c> and it's as easy as: |
| 88 |
+The function we should use to do this is <c>depends</c> and it's as easy as: |
| 89 |
</p> |
| 90 |
|
| 91 |
<pre caption="Looking for packages depending on pygtk"> |
| 92 |
@@ -205,8 +205,8 @@ |
| 93 |
<body> |
| 94 |
|
| 95 |
<p> |
| 96 |
-<c>equery</c> is capable of giving us a dependency graph for a specified |
| 97 |
-package. The dependency graph gives a listing of all the packages that have |
| 98 |
+<c>equery</c> is capable of giving us a dependency graph for a specified |
| 99 |
+package. The dependency graph gives a listing of all the packages that have |
| 100 |
direct and indirect dependencies on the package in question. |
| 101 |
</p> |
| 102 |
|
| 103 |
@@ -231,11 +231,11 @@ |
| 104 |
</pre> |
| 105 |
|
| 106 |
<p> |
| 107 |
-For example, while glibc is a direct dependency for cdrtools,linux-headers |
| 108 |
-are an indirect dependency. Note that the output also includes information |
| 109 |
-about virtual packages. In the example above, <c>cdrtools</c> is actually |
| 110 |
-written to require virtual/libc, not sys-libs/glibc, but on the given |
| 111 |
-system in the example sys-libs/glibc provides virtual/libc. |
| 112 |
+For example, while glibc is a direct dependency for cdrtools,linux-headers |
| 113 |
+are an indirect dependency. Note that the output also includes information |
| 114 |
+about virtual packages. In the example above, <c>cdrtools</c> is actually |
| 115 |
+written to require virtual/libc, not sys-libs/glibc, but on the given |
| 116 |
+system in the example sys-libs/glibc provides virtual/libc. |
| 117 |
</p> |
| 118 |
|
| 119 |
</body> |
| 120 |
@@ -245,7 +245,7 @@ |
| 121 |
<body> |
| 122 |
|
| 123 |
<p> |
| 124 |
-<c>equery</c> can list the files that belong to an installed ebuild. If I |
| 125 |
+<c>equery</c> can list the files that belong to an installed ebuild. If I |
| 126 |
don't know the files that Gentoolkit has installed on the system, I will |
| 127 |
use <c>equery</c> to show them. |
| 128 |
</p> |
| 129 |
@@ -280,7 +280,7 @@ |
| 130 |
</pre> |
| 131 |
|
| 132 |
<p> |
| 133 |
-The command <c>files</c> of <c>equery</c> provide some options to modify |
| 134 |
+The command <c>files</c> of <c>equery</c> provide some options to modify |
| 135 |
the output. You can look them all up in the <c>equery</c> man page. |
| 136 |
</p> |
| 137 |
|
| 138 |
@@ -291,7 +291,7 @@ |
| 139 |
<body> |
| 140 |
|
| 141 |
<p> |
| 142 |
-If you want to find which packages on your system that make use of a specific |
| 143 |
+If you want to find which packages on your system that make use of a specific |
| 144 |
USE flag, <c>equery</c> has the function <c>hasuse</c>: |
| 145 |
</p> |
| 146 |
|
| 147 |
@@ -310,7 +310,7 @@ |
| 148 |
<body> |
| 149 |
|
| 150 |
<p> |
| 151 |
-<c>equery</c> has a power feature to list packages belonging to our system, |
| 152 |
+<c>equery</c> has a power feature to list packages belonging to our system, |
| 153 |
portage or even an overlay. Let's try this: |
| 154 |
</p> |
| 155 |
|
| 156 |
@@ -322,11 +322,11 @@ |
| 157 |
</pre> |
| 158 |
|
| 159 |
<p> |
| 160 |
-The standard query will search our installed packages for the name given. |
| 161 |
-If found, the following info will be displayed: the package location between |
| 162 |
-the first square brackets (I for Installed packages, P for Portage, O for |
| 163 |
-Overlay), the possible masks between the second (~ by keyword, - by arch or |
| 164 |
-M hard masked), then the category and complete name and last of all, the slot |
| 165 |
+The standard query will search our installed packages for the name given. |
| 166 |
+If found, the following info will be displayed: the package location between |
| 167 |
+the first square brackets (I for Installed packages, P for Portage, O for |
| 168 |
+Overlay), the possible masks between the second (~ by keyword, - by arch or |
| 169 |
+M hard masked), then the category and complete name and last of all, the slot |
| 170 |
in which the package is stored. |
| 171 |
</p> |
| 172 |
|
| 173 |
@@ -374,7 +374,7 @@ |
| 174 |
</pre> |
| 175 |
|
| 176 |
<p> |
| 177 |
-As you can see, <c>equery</c> prints the total space used in kilobytes and |
| 178 |
+As you can see, <c>equery</c> prints the total space used in kilobytes and |
| 179 |
also lists the total number of files the package has. |
| 180 |
</p> |
| 181 |
|
| 182 |
@@ -385,8 +385,8 @@ |
| 183 |
<body> |
| 184 |
|
| 185 |
<p> |
| 186 |
-<c>equery</c> can be used to give us information about what USE flags |
| 187 |
-are being used by a specific package. It also tells us what our current USE |
| 188 |
+<c>equery</c> can be used to give us information about what USE flags |
| 189 |
+are being used by a specific package. It also tells us what our current USE |
| 190 |
flags are for a package and also what USE flags are available for the package. |
| 191 |
</p> |
| 192 |
|
| 193 |
@@ -446,7 +446,7 @@ |
| 194 |
<p> |
| 195 |
<c>euse</c> is a tool to see, set and unset USE flags at various places. For |
| 196 |
more information on USE flags, please refer to the <uri |
| 197 |
-link="/doc/en/handbook/handbook-x86.xml?part=2&chap=2">USE Flags</uri>. |
| 198 |
+link="/doc/en/handbook/handbook-x86.xml?part=2&chap=2">USE Flags</uri>. |
| 199 |
Please see <c>euse -h</c> for complete help and all options. |
| 200 |
</p> |
| 201 |
|
| 202 |
@@ -457,15 +457,15 @@ |
| 203 |
<body> |
| 204 |
|
| 205 |
<p> |
| 206 |
-The <c>euse -a</c> command reads the current active USE flags and displays |
| 207 |
+The <c>euse -a</c> command reads the current active USE flags and displays |
| 208 |
them. |
| 209 |
</p> |
| 210 |
|
| 211 |
<note> |
| 212 |
-There are 5 "columns" that <c>euse</c> now uses to show whether a |
| 213 |
-flag is set/unset and where all the flag has been set. The columns are as |
| 214 |
-follows -- +/-, set in the Environment, set in make.Conf, set in make.Defaults, |
| 215 |
-and set in make.Globals. The output looks like [+ECDG]. |
| 216 |
+There are 5 "columns" that <c>euse</c> now uses to show whether a |
| 217 |
+flag is set/unset and where all the flag has been set. The columns are as |
| 218 |
+follows -- +/-, set in the Environment, set in make.Conf, set in make.Defaults, |
| 219 |
+and set in make.Globals. The output looks like [+ECDG]. |
| 220 |
</note> |
| 221 |
|
| 222 |
<pre caption="Viewing all active USE flags"> |
| 223 |
@@ -563,9 +563,9 @@ |
| 224 |
</pre> |
| 225 |
|
| 226 |
<p> |
| 227 |
-Similarly you can use the <c>euse -a -g</c> command to only view active global |
| 228 |
-USE flags. The <c>euse -a -l</c> command does the same for active local USE |
| 229 |
-flags.<c>-g</c> & <c>-l</c> are suboptions to <c>euse</c> and need an |
| 230 |
+Similarly you can use the <c>euse -a -g</c> command to only view active global |
| 231 |
+USE flags. The <c>euse -a -l</c> command does the same for active local USE |
| 232 |
+flags.<c>-g</c> & <c>-l</c> are suboptions to <c>euse</c> and need an |
| 233 |
option before them (like <c>-a</c>) to function correctly. |
| 234 |
</p> |
| 235 |
|
| 236 |
@@ -583,15 +583,15 @@ |
| 237 |
</pre> |
| 238 |
|
| 239 |
<p> |
| 240 |
-We can also use <c>euse</c> to set or unset use flags. The commands used for |
| 241 |
-this are <c>euse -E flagname</c> (enable a flag) and <c>euse -D flagname</c> |
| 242 |
+We can also use <c>euse</c> to set or unset use flags. The commands used for |
| 243 |
+this are <c>euse -E flagname</c> (enable a flag) and <c>euse -D flagname</c> |
| 244 |
(disable a flag). |
| 245 |
</p> |
| 246 |
|
| 247 |
<warn> |
| 248 |
-Do not use the <c>euse -E</c> or <c>euse -D</c> commands by themselves (without |
| 249 |
-a flag). It will set/unset ALL USE flags in <c>/etc/make.conf</c>. Although a |
| 250 |
-backup is kept at <path>/etc/make.conf.euse_backup</path>, please be careful |
| 251 |
+Do not use the <c>euse -E</c> or <c>euse -D</c> commands by themselves (without |
| 252 |
+a flag). It will set/unset ALL USE flags in <c>/etc/make.conf</c>. Although a |
| 253 |
+backup is kept at <path>/etc/make.conf.euse_backup</path>, please be careful |
| 254 |
while using <c>euse -E</c> or <c>euse -D</c>. |
| 255 |
</warn> |
| 256 |
|
| 257 |
@@ -691,21 +691,21 @@ |
| 258 |
All prepared. Starting rebuild... |
| 259 |
emerge --oneshot --nodeps -p =app-cdr/k3b-0.11.14 =app-office/koffice-1.3.2 =app-office/lyx-1.3.4 \ |
| 260 |
=app-office/passepartout-0.2 =dev-lang/lua-5.0.2 =dev-ruby/fxruby-1.0.29 =media-libs/libao-0.8.5 \ |
| 261 |
- =media-libs/xine-lib-1_rc5-r3 =media-video/avidemux-2.0.26 =net-libs/loudmouth-0.16 |
| 262 |
+ =media-libs/xine-lib-1_rc5-r3 =media-video/avidemux-2.0.26 =net-libs/loudmouth-0.16 |
| 263 |
|
| 264 |
These are the packages that I would merge, in order: |
| 265 |
|
| 266 |
Calculating dependencies ...done! |
| 267 |
-[ebuild R ] app-cdr/k3b-0.11.14 |
| 268 |
-[ebuild R ] app-office/koffice-1.3.2 |
| 269 |
-[ebuild R ] app-office/lyx-1.3.4 |
| 270 |
-[ebuild R ] app-office/passepartout-0.2 |
| 271 |
-[ebuild R ] dev-lang/lua-5.0.2 |
| 272 |
-[ebuild R ] dev-ruby/fxruby-1.0.29 |
| 273 |
-[ebuild R ] media-libs/libao-0.8.5 |
| 274 |
-[ebuild R ] media-libs/xine-lib-1_rc5-r3 |
| 275 |
-[ebuild R ] media-video/avidemux-2.0.26 |
| 276 |
-[ebuild R ] net-libs/loudmouth-0.16 |
| 277 |
+[ebuild R ] app-cdr/k3b-0.11.14 |
| 278 |
+[ebuild R ] app-office/koffice-1.3.2 |
| 279 |
+[ebuild R ] app-office/lyx-1.3.4 |
| 280 |
+[ebuild R ] app-office/passepartout-0.2 |
| 281 |
+[ebuild R ] dev-lang/lua-5.0.2 |
| 282 |
+[ebuild R ] dev-ruby/fxruby-1.0.29 |
| 283 |
+[ebuild R ] media-libs/libao-0.8.5 |
| 284 |
+[ebuild R ] media-libs/xine-lib-1_rc5-r3 |
| 285 |
+[ebuild R ] media-video/avidemux-2.0.26 |
| 286 |
+[ebuild R ] net-libs/loudmouth-0.16 |
| 287 |
|
| 288 |
Now you can remove -p (or --pretend) from arguments and re-run revdep-rebuild. |
| 289 |
</pre> |
| 290 |
@@ -761,7 +761,8 @@ |
| 291 |
<pre caption="Using eread"> |
| 292 |
$ <i>eread</i> |
| 293 |
|
| 294 |
-This is a list of portage log items. Choose a number to view that file or type q to quit. |
| 295 |
+This is a list of portage log items. Choose a number to view that file or type |
| 296 |
+q to quit. |
| 297 |
|
| 298 |
1) app-portage:gentoolkit-0.2.4_pre2:20070320-000256.log |
| 299 |
2) app-portage:gentoolkit-0.2.4_pre2:20070320-000258.log |
| 300 |
|
| 301 |
|
| 302 |
|
| 303 |
-- |
| 304 |
gentoo-doc-cvs@l.g.o mailing list |
Archives