From: "Michał Górny" <mgorny@gentoo.org>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: "gentoo-portage-dev@lists.gentoo.org"
<gentoo-portage-dev@lists.gentoo.org>
Subject: Re: [gentoo-portage-dev] distfiles in overlays?
Date: Tue, 3 Nov 2015 13:38:33 +0100 [thread overview]
Message-ID: <20151103133833.09e35241.mgorny@gentoo.org> (raw)
In-Reply-To: <1446553740.21216.72.camel@transmode.se>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Tue, 3 Nov 2015 12:29:01 +0000
Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:
> Sometimes I have to move files from my layman overlays distfiles to /usr/portage/distfiles
> in orders to rebuild older stuff not in gentoo anymore.
>
> Should not emerge search in distfiles where the ebuild resides?
distfiles are not part of repository. The /usr/portage/distfiles path
is just wrong and you shouldn't be using it.
> What about eclass? What is the search order here?
It follows masters. First the repository with ebuild. If it's not
there, it looks through all masters, then their masters etc.
> If I got a customized user.eclass in my overlay, can I have this eclass take
> precedence over the one in /usr/portage/eclass ?
Yes. 'man 5 portage', look for eclass-overrides. Note that this will
effectively discard metadata cache and therefore make stuff slow after
syncing .
--
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
next prev parent reply other threads:[~2015-11-03 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 12:29 [gentoo-portage-dev] distfiles in overlays? Joakim Tjernlund
2015-11-03 12:38 ` Michał Górny [this message]
2015-11-03 16:51 ` Joakim Tjernlund
2015-11-03 17:51 ` Alex Brandt
2015-11-03 18:04 ` Brian Dolbec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151103133833.09e35241.mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
--cc=joakim.tjernlund@transmode.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox