From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Needs ideas: Upcoming circular dependency: expat <> CMake
Date: Thu, 19 Dec 2019 15:39:50 +0100 [thread overview]
Message-ID: <8a987393-685c-b9d8-df19-471603fbe10b@gentoo.org> (raw)
In-Reply-To: <b5be4d4b2df2c96028451688b07cc21489ddf278.camel@gentoo.org>
Hey!
Thanks everyone for your thoughts so far!
From what I heard, these two options seem realistic to me:
A) Ask the KDE team for help with teaming up on a new package
dev-util/cmake-bootstrap, keep it in sync with dev-util/cmake,
make sure both packages co-exists with full disjoint operation,
i.e. zero file conflicts + zero cross package file usage (tricky?).
B) Introduce USE flag "system-expat" to CMake similar to existing
flag "system-jsoncpp", have it off by default, keep reminding
CMake upstream to update their bundle
I favor (B) by more than just a bit. Does anyone have strong concerns
against moving in the dev-util/cmake[-system-expat] (B) direction? Is
it acceptable if I make those changes to the CMake ebuild myself?
Thanks again
Sebastian
next prev parent reply other threads:[~2019-12-19 14:39 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
2019-12-19 8:31 ` Michał Górny
2019-12-19 14:39 ` Sebastian Pipping [this message]
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=8a987393-685c-b9d8-df19-471603fbe10b@gentoo.org \
--to=sping@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