/[gentoo]/xml/htdocs/doc/en/handbook/hb-working-portage.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-working-portage.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.40 Revision 1.46
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.40 2004/10/21 16:34:46 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.46 2004/12/18 15:12:22 neysx Exp $ -->
8 8
9<sections> 9<sections>
10
11<version>1.42</version>
12<date>2004-10-24</date>
13
10<section> 14<section>
11<title>Welcome to Portage</title> 15<title>Welcome to Portage</title>
12<body> 16<body>
13 17
14<p> 18<p>
94<body> 98<body>
95 99
96<p> 100<p>
97To search through the Portage tree after software titles, you can use 101To search through the Portage tree after software titles, you can use
98<c>emerge</c> built-in search capabilities. By default, <c>emerge search</c> 102<c>emerge</c> built-in search capabilities. By default, <c>emerge search</c>
99returns package names whos title corresponds with (either fully or partially) 103returns the names of packages whose title matches (either fully or partially)
100the given search term. 104the given search term.
101</p> 105</p>
102 106
103<p> 107<p>
104For instance, to search for all packages who have "pdf" in their name: 108For instance, to search for all packages who have "pdf" in their name:
304<body> 308<body>
305 309
306<p> 310<p>
307As we stated before, Portage is extremely powerful and supports many features 311As we stated before, Portage is extremely powerful and supports many features
308that other software management tools lack. To understand this, we explain a few 312that other software management tools lack. To understand this, we explain a few
309aspects of Portage without going in too much detail. 313aspects of Portage without going into too much detail.
310</p> 314</p>
311 315
312<p> 316<p>
313With Portage different versions of a single package can coexist on a system. 317With Portage different versions of a single package can coexist on a system.
314While other distributions tend to name their package to those versions (like 318While other distributions tend to name their package to those versions (like
365!!! both can't be installed on the same system together. 369!!! both can't be installed on the same system together.
366!!! Please use 'emerge --pretend' to determine blockers. 370!!! Please use 'emerge --pretend' to determine blockers.
367</pre> 371</pre>
368 372
369<p> 373<p>
370Ebuilds contain specific fields that inform Portage about it's dependencies. 374Ebuilds contain specific fields that inform Portage about its dependencies.
371There are two possible dependencies: build dependencies, declared in 375There are two possible dependencies: build dependencies, declared in
372<c>DEPEND</c> and run-time dependencies, declared in <c>RDEPEND</c>. When one of 376<c>DEPEND</c> and run-time dependencies, declared in <c>RDEPEND</c>. When one of
373these dependencies explicitly marks a package or virtual as being <e>not</e> 377these dependencies explicitly marks a package or virtual as being <e>not</e>
374compatible, it triggers a blockage. 378compatible, it triggers a blockage.
375</p> 379</p>

Legend:
Removed from v.1.40  
changed lines
  Added in v.1.46

  ViewVC Help
Powered by ViewVC 1.1.20