Thanks,
I think this will help me a to make the work done.
If I'll have a lot of time (counting 2222 February 22. ;o( ) I'll have a
look at this all.
Frank
On Tue, 2005-02-15 at 17:03 +0100, Holly Bostick wrote:
> Frank Schafer wrote:
> > Thanks a lot.
> >
> > Could you tell me what the PORTDIR_OVERLAY is?
>
> The PORTDIR_OVERLAY variable is set in /etc/make.conf. It references the
> directory (usually /usr/local/portage, but you can set it to be wherever
> you want via this variable), where you keep ebuilds that don't *belong*
> to Portage (meaning, they did not come via an emerge sync, but were
> downloaded from a site that has them, such as bugs.gentoo.org, or
> breakmygentoo.net, some private sites run by gentoo users that carry
> ebuilds for individual programs, or did come from Portage originally,
> but were edited by you), but should be managed by Portage (meaning that
> ebuilds installed from the PORTDIR_OVERLAY will be known to Portage, and
> can 'override' Portage ebuilds (if you edit the development-sources
> ebuild and put it in your overlay, it will be newer than the ebuild in
> regular Portage, so it will be chosen first when you request to install
> development-sources). The emerge output will note that the proposed
> emerge will come from your overlay, and which one (you can have multiple
> overlay sources, such as your privately downloaded ones in
> /usr/local/portage, and the more automated sources from
> breakmygentoo.net, which has its own emerge-style system-- gensync,
> iirc-- to update their available ebuild tree).
>
>
>
> >
> > I read the ebuild of the gemtoo-dev-sources just now.
> >
> > Well, there are 2 tarballs with patches. Can someone tell me where
> > ${DISTDIR} is? I'd like to have a look at the tarballs to at least know
> > what I'm patching. ... or where do I find the genpatches-*?
> > ... and where is ${WORKDIR}? Maybe the 0000_README will tell me what I
> > want to know.
>
>
> These variables are all set in /etc/make.conf, except for ${WORKDIR},
> which is set in the ebuild.
>
> Part of my /etc/make.conf:
>
> PORTAGE_TMPDIR=/var/tmp
> PORTDIR=/usr/portage
> DISTDIR=${PORTDIR}/distfiles
> PKGDIR=${PORTDIR}/packages
> PORT_LOGDIR=/var/log/portage
> PORTDIR_OVERLAY="/usr/local/portage /usr/local/bmg-main"
>
> So, as you see, ${DISTDIR} is in ${PORTDIR}/distfiles, which expands to
> /usr/portage/distfiles, which is where all downloaded tarballs live.
>
> ${WORKDIR} is a temporary directory where the compiling actually takes
> place; it has to be set by the ebuild because the path contains the name
> and version number of the ebuild, which are a variable contained in the
> ebuild. It's someplace in /var/tmp (sorry, can't check atm), and is
> 'cleaned out' when the compile completes successfully (and left there,
> hogging up space, if the compile fails).
>
>
> You might want to have a look at the "Working With Portage" docs at
> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3 .
>
> HTH,
> Holly
> --
> [email protected] mailing list
>
--
Frank Schafer
System specialist
T-Systems Czech s.r.o.
Kloboučnická 1435/24, 140 00 Praha 4
Tel.: +420 296529522
Fax: +420 296529129
Mobil: +420 605 202 419
E-mail: [EMAIL PROTECTED]
Internet: http://www.t-systems.cz
--
[email protected] mailing list
