From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Broken binary packages
Date: Sat, 18 Jul 2020 06:51:05 -0400 [thread overview]
Message-ID: <CAGfcS_mhiGM_Ga44p=JnxLCzbNhtmsa_SRS+5PRvQeEYM23mug@mail.gmail.com> (raw)
In-Reply-To: <2770600.irdbgypaU6@zeus>
On Sat, Jul 18, 2020 at 6:36 AM Alexander Puchmayr
<alexander.puchmayr@linznet.at> wrote:
>
> Is there a better way to solve this? Is it possible to tell mythtv's build
> system to ignore the unwanted libraries if the xmltv use-flag is NOT set?
Maybe, and if you do please do submit a patch.
We refer to these sorts of build systems as "automagic" and they can
be pretty problematic in situations like this.
There are really only two ways to go about fixing this sort of thing
systematically at a Gentoo level:
1. Go and patch all the build systems not to behave this way, or
discover all the necessary override options (if available) and pass
every one of them. This is the current preferred way and has
everybody's full support, but it isn't easy and so it often doesn't
happen.
2. Change portage to either use mount namespaces or the sandbox to
prevent anything not in a specified dependency (which could include
@system) from being seen or read at build time. IMO this is the
cleaner solution and some other distros do it this way. As a
side-effect it would probably eliminate a lot of bugs where deps were
missed in the ebuild. This should defeat most problems with automagic
build systems.
Right now you're either going to have to fix the ebuild yourself (and
please submit a bug with the fix), or keep your hosts more in sync so
that the same binary works on both.
--
Rich
prev parent reply other threads:[~2020-07-18 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 10:36 [gentoo-user] Broken binary packages Alexander Puchmayr
2020-07-18 10:51 ` Rich Freeman [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='CAGfcS_mhiGM_Ga44p=JnxLCzbNhtmsa_SRS+5PRvQeEYM23mug@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@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