From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] about modifying an ebuild in local overlay and $FILESDIR
Date: Wed, 26 Apr 2017 16:28:03 -0400 [thread overview]
Message-ID: <CAJ0EP43ZasbhsY8WPYKo1Lj108HBqXcWe4QudAuX=T43Vu+P7w@mail.gmail.com> (raw)
In-Reply-To: <f864315a-d74c-cc5d-55f7-341c7f3addd1@bricart.de>
On Wed, Apr 26, 2017 at 4:03 PM, Christian Bricart <christian@bricart.de> wrote:
> Hi all,
>
> from time to time, I need to make (and maintain) modifications to an
> ebuild from the main tree in my local overlay.
> So basically, I create the directory structure from
> /usr/portage/<category>/<package>/ under
> /usr/local/portage/<category>/<package>/, copy over the ebuild and do my
> modifications in the ebuild.
> So far how an overlay works ;-)
>
> But if there are references to patches, init-scripts, conf-files, etc
> from $FILESDIR w/i the original ebuild, one also needs to copy those
> into /usr/local/portage/../../files/ ..
>
> Is it possible to "overlay" such files used in epatch(), newins(),
> newconfd(), newinitd(), etc too..?
>
> so i.e:
> FILESDIR = "${repository_location}/${CATEGORY}/${PN}/files"
> should support a fallback to:
> FILESDIR = "${PORTDIR}/${CATEGORY}/${PN}/files"
> if not found...
> (or actually to the defined $master from the repo used)
No, this is not possible. It might be possible to implement in
portage, but I don't think it's a very good/workable idea.
As a workaround, you could symlink individual files, or even the
entire files directory.
prev parent reply other threads:[~2017-04-26 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 20:03 [gentoo-dev] about modifying an ebuild in local overlay and $FILESDIR Christian Bricart
2017-04-26 20:28 ` Mike Gilbert [this message]
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='CAJ0EP43ZasbhsY8WPYKo1Lj108HBqXcWe4QudAuX=T43Vu+P7w@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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