/[gentoo]/xml/htdocs/doc/en/faq.xml
Gentoo

Diff of /xml/htdocs/doc/en/faq.xml

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

Revision 1.44 Revision 1.45
13<author title="Editor"><mail link="swift@gentoo.org">Sven Vermeulen</mail></author> 13<author title="Editor"><mail link="swift@gentoo.org">Sven Vermeulen</mail></author>
14<abstract>This FAQ is a collection of questions and answers collected from the gentoo-dev mailing list and from IRC -- if you have any questions (or answers!) to add, please contact either an author or a member of the documentation team.</abstract> 14<abstract>This FAQ is a collection of questions and answers collected from the gentoo-dev mailing list and from IRC -- if you have any questions (or answers!) to add, please contact either an author or a member of the documentation team.</abstract>
15 15
16<license/> 16<license/>
17 17
18<version>1.1.9</version> 18<version>1.1.10</version>
19<date>November 06, 2003</date> 19<date>November 7, 2003</date>
20 20
21<chapter> 21<chapter>
22<title>Featured Questions</title> 22<title>Featured Questions</title>
23<section> 23<section>
24<title>Getting Started</title> 24<title>Getting Started</title>
516 </p></body> 516 </p></body>
517 </section> 517 </section>
518 518
519 <section> 519 <section>
520 <title>I want to perform the <c>./configure</c> step myself. Can I?</title> 520 <title>I want to perform the <c>./configure</c> step myself. Can I?</title>
521 <body><p> 521 <body>
522 Yes, but it is not trivial. First do <c>man ebuild</c> followed by 522<p>
523 <c>ebuild foo-x.y.z.ebuild unpack</c>. Then <c>cd</c> to 523Yes, but it is not trivial, and the next method only works when it is a simple
524 <path>/var/tmp/portage/foo-x.y.z/work</path>. You can manually perform 524ebuild (i.e. just <c>./configure</c> and <c>make &amp;&amp; make install</c>).
525 the <c>./configure</c> and <c>make</c> steps yourself (you'll have to do 525Be sure to read the ebuild itself to see how Gentoo handles it.
526 both, since Portage does not separate the configure and build steps). To 526</p>
527 have Portage finish the installation (so that you can easily remove it later, 527
528 should you desire to do so, and it will be registered in Portage as a possible 528<p>
529 dependency) you first need to <c>touch /var/tmp/portage/foo-x.y.z/.compiled</c> 529Start with unpacking the ebuild: <c>ebuild
530 (tricking Portage into thinking that <c>ebuild foo-x.y.z.ebuild compile</c> has 530/usr/portage/&lt;category&gt;/&lt;package&gt;/&lt;ebuild&gt; unpack</c>.
531 completed), followed by <c>ebuild foo-x.y.z.ebuild merge</c>. 531</p>
532 </p></body> 532
533<p>
534Next, go to <path>/var/tmp/portage/&lt;package&gt;-&lt;version&gt;/work</path>.
535Inside it you'll find the unpacked sources. Execute the steps you need to
536perform to configure and compile the package.
537</p>
538
539<p>
540When finished, execute <c>touch
541/var/tmp/portage/&lt;package&gt;-&lt;version&gt;/.compiled</c> to trick Portage
542into thinking it configured and compiled the package. Then finish up with
543<c>ebuild /usr/portage/&lt;category&gt;/&lt;package&gt;/&lt;ebuild&gt;
544merge</c>.
545</p>
546
547 </body>
533 </section> 548 </section>
534 549
535 <section> 550 <section>
536 <title>What if rsync doesn't work for me?</title> 551 <title>What if rsync doesn't work for me?</title>
537 <body><p> 552 <body><p>

Legend:
Removed from v.1.44  
changed lines
  Added in v.1.45

  ViewVC Help
Powered by ViewVC 1.1.20