Re: [gentoo-user] Locations used by emerge/ebuild?

2003-07-23 Thread brett holcomb
You're very welcome. Yes, emerge/ebuild will clean out the files unless you put noclean (I'm going by memory as I'm not at a gentoo machine) in FEATURES in /etc/make.conf. That tells them to leave the files behind. On 22 Jul 2003 20:13:17 -0700 Mark Knecht <[EMAIL PROTECTED]> wrote: On Tu

Re: [gentoo-user] Locations used by emerge/ebuild?

2003-07-22 Thread Mark Knecht
Brett, Marius, Donnie, Christopher & Dan, Thanks for the great descriptions! I've got the source unpacked now and am working on trying to apply the patches and replacing a few files. Hopefully I can get this part handled and try the ebuild qmerge step later this evening. Thanks for all your

Re: [gentoo-user] Locations used by emerge/ebuild?

2003-07-22 Thread Dan Foster
Hot Diggety! Mark Knecht was rumored to have written: > > WORKDIR seems to work out to /var/tmp/portage//work, which Aye, that is correct. > Has some process cleaned this up? Maybe this is my problem? I'm trying Aye, that is also correct. After a successful emerge, it deletes the work director

Re: [gentoo-user] Locations used by emerge/ebuild?

2003-07-22 Thread Christopher Egner
On Tue, 2003-07-22 at 22:13, Mark Knecht wrote: > On Tue, 2003-07-22 at 19:37, Brett I. Holcomb wrote: > > Check out man 1 ebuild and man 5 ebuild. It uses directories in /var/tmp. > > > > The source itself (if it's a tarball) is kept in /usr/portage/distfiles. Cvs > > stuff in in the distfiles

Re: [gentoo-user] Locations used by emerge/ebuild?

2003-07-22 Thread donnie berkholz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 22 July 2003 22:13, Mark Knecht wrote: > WORKDIR seems to work out to /var/tmp/portage//work, which > doesn't exist on my machine: > > Wizard alsa-driver # cd /var/tmp/portage/alsa-driver-0.9.5-r2/ > Wizard alsa-driver-0.9.5-r2 # ls > temp >

Re: [gentoo-user] Locations used by emerge/ebuild?

2003-07-22 Thread Marius Mauch
On 07/22/03 Mark Knecht wrote: > WORKDIR = "${PORTAGE_TMPDIR}/portage/${PF}/work" > or > FILESDIR = "${PORTDIR}/${CATEGORY}/${PN}/files" > > WORKDIR seems to work out to /var/tmp/portage//work, which > doesn't exist on my machine: > > Wizard alsa-driver # cd /var/tmp/portage/alsa-driver-0.9.5

Re: [gentoo-user] Locations used by emerge/ebuild?

2003-07-22 Thread Mark Knecht
On Tue, 2003-07-22 at 19:37, Brett I. Holcomb wrote: > Check out man 1 ebuild and man 5 ebuild. It uses directories in /var/tmp. > > The source itself (if it's a tarball) is kept in /usr/portage/distfiles. Cvs > stuff in in the distfiles under cvs-src. > > The variables are defined in /etc/ma

Re: [gentoo-user] Locations used by emerge/ebuild?

2003-07-22 Thread Brett I. Holcomb
Check out man 1 ebuild and man 5 ebuild. It uses directories in /var/tmp. The source itself (if it's a tarball) is kept in /usr/portage/distfiles. Cvs stuff in in the distfiles under cvs-src. The variables are defined in /etc/make.conf - see the comments in it and by the ebuild programs them

[gentoo-user] Locations used by emerge/ebuild?

2003-07-22 Thread Mark Knecht
Hi, I'm looking for the location that emerge/ebuild places the source code prior to building it. 1) I've found the ebuild itself in /usr/portage// and... 2) I've found the tarball in /usr/portage/distfiles but... I cannot spot where the source itself actually resides. Unfortunately for me