| 1 |
On Wed, Apr 26, 2017 at 4:03 PM, Christian Bricart <christian@×××××××.de> wrote: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> from time to time, I need to make (and maintain) modifications to an |
| 5 |
> ebuild from the main tree in my local overlay. |
| 6 |
> So basically, I create the directory structure from |
| 7 |
> /usr/portage/<category>/<package>/ under |
| 8 |
> /usr/local/portage/<category>/<package>/, copy over the ebuild and do my |
| 9 |
> modifications in the ebuild. |
| 10 |
> So far how an overlay works ;-) |
| 11 |
> |
| 12 |
> But if there are references to patches, init-scripts, conf-files, etc |
| 13 |
> from $FILESDIR w/i the original ebuild, one also needs to copy those |
| 14 |
> into /usr/local/portage/../../files/ .. |
| 15 |
> |
| 16 |
> Is it possible to "overlay" such files used in epatch(), newins(), |
| 17 |
> newconfd(), newinitd(), etc too..? |
| 18 |
> |
| 19 |
> so i.e: |
| 20 |
> FILESDIR = "${repository_location}/${CATEGORY}/${PN}/files" |
| 21 |
> should support a fallback to: |
| 22 |
> FILESDIR = "${PORTDIR}/${CATEGORY}/${PN}/files" |
| 23 |
> if not found... |
| 24 |
> (or actually to the defined $master from the repo used) |
| 25 |
|
| 26 |
No, this is not possible. It might be possible to implement in |
| 27 |
portage, but I don't think it's a very good/workable idea. |
| 28 |
|
| 29 |
As a workaround, you could symlink individual files, or even the |
| 30 |
entire files directory. |
Archives