From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Needs ideas: Upcoming circular dependency: expat <> CMake
Date: Thu, 19 Dec 2019 14:38:14 +1300 [thread overview]
Message-ID: <20191219143814.0c8c59cf@katipo2.lan> (raw)
In-Reply-To: <20191218235822.5b036cf2@sf>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
On Wed, 18 Dec 2019 23:58:22 +0000
Sergei Trofimovich <slyfox@gentoo.org> wrote:
> [c] would be nice to be solved at portage level if portage could schedule
> multiple merges for the same package with different USE flags.
Related bugs:
- Portage should be able to auto-flip USE="test" & FEATURES="test"
https://bugs.gentoo.org/697914#c0
- Portage needs an extension to package.use specification to provide a
level of discretion to portage to flip flags on its own
https://bugs.gentoo.org/698920#c0
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-19 1:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a722f8f-36b5-c313-b6e1-eac75e0839c5@gentoo.org>
2019-12-18 21:02 ` [gentoo-dev] Needs ideas: Upcoming circular dependency: expat <> CMake Sebastian Pipping
2019-12-18 21:08 ` Michał Górny
2019-12-18 21:10 ` Piotr Karbowski
2019-12-18 21:14 ` Michał Górny
2019-12-18 21:44 ` Francesco Riosa
2019-12-19 13:32 ` Rolf Eike Beer
2019-12-19 14:18 ` Sebastian Pipping
2019-12-18 23:58 ` Sergei Trofimovich
2019-12-19 1:38 ` Kent Fredric [this message]
2019-12-19 8:31 ` Michał Górny
2019-12-19 14:39 ` Sebastian Pipping
2019-12-19 16:03 ` Michał Górny
2019-12-19 17:28 ` Sebastian Pipping
2019-12-19 17:37 ` Michał Górny
2019-12-19 18:43 ` Sebastian Pipping
2019-12-19 19:21 ` Michał Górny
2019-12-20 13:41 ` Gerion Entrup
2019-12-20 14:25 ` Rich Freeman
2019-12-19 21:28 ` Michael Orlitzky
2019-12-19 0:19 ` Michael Orlitzky
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=20191219143814.0c8c59cf@katipo2.lan \
--to=kentnl@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