| 1 |
On Sat, Jul 18, 2020 at 6:36 AM Alexander Puchmayr |
| 2 |
<alexander.puchmayr@×××××××.at> wrote: |
| 3 |
> |
| 4 |
> Is there a better way to solve this? Is it possible to tell mythtv's build |
| 5 |
> system to ignore the unwanted libraries if the xmltv use-flag is NOT set? |
| 6 |
|
| 7 |
Maybe, and if you do please do submit a patch. |
| 8 |
|
| 9 |
We refer to these sorts of build systems as "automagic" and they can |
| 10 |
be pretty problematic in situations like this. |
| 11 |
|
| 12 |
There are really only two ways to go about fixing this sort of thing |
| 13 |
systematically at a Gentoo level: |
| 14 |
|
| 15 |
1. Go and patch all the build systems not to behave this way, or |
| 16 |
discover all the necessary override options (if available) and pass |
| 17 |
every one of them. This is the current preferred way and has |
| 18 |
everybody's full support, but it isn't easy and so it often doesn't |
| 19 |
happen. |
| 20 |
2. Change portage to either use mount namespaces or the sandbox to |
| 21 |
prevent anything not in a specified dependency (which could include |
| 22 |
@system) from being seen or read at build time. IMO this is the |
| 23 |
cleaner solution and some other distros do it this way. As a |
| 24 |
side-effect it would probably eliminate a lot of bugs where deps were |
| 25 |
missed in the ebuild. This should defeat most problems with automagic |
| 26 |
build systems. |
| 27 |
|
| 28 |
Right now you're either going to have to fix the ebuild yourself (and |
| 29 |
please submit a bug with the fix), or keep your hosts more in sync so |
| 30 |
that the same binary works on both. |
| 31 |
|
| 32 |
-- |
| 33 |
Rich |
Archives