From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Needs ideas: Upcoming circular dependency: expat <> CMake
Date: Thu, 19 Dec 2019 18:37:28 +0100 [thread overview]
Message-ID: <fb46f0c2fc95f798e4b09005d8cb1ff185f62750.camel@gentoo.org> (raw)
In-Reply-To: <1c21f87e-ccea-cabc-5c19-1414aaf029a5@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
On Thu, 2019-12-19 at 18:28 +0100, Sebastian Pipping wrote:
> Hey!
>
>
> On 19.12.19 17:03, Michał Górny wrote:
> > > 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
> > >
> > > [..]
> >
> > It violates the policy on bundled libraries.
>
> Same for the dev-util/cmake-bootstrap approach, right?
>
>
> > What's worse, the awful
> > USE flags solution means that most of the Gentoo devs end up using
> > bundled libraries just because people are manually required to figure
> > out what to do in order to disable them.
>
> I didn't say that it's perfect :) It's the same approach that we have
> have with the system-jsoncpp USE flag already so that was considered
> good enough at some point in the past. I guess we want the same for
> Expat and jsoncpp? Which alternative do you see as better than a new
> flag system-expat?
>
Just because someone did something crappy, it doesn't mean it was
considered 'good enough'. It was just a cheap hack that someone once
did just to get it over with and stop caring. Not a good solution we
should keep copying.
We have a better alternative that lets us limit the impact on the users.
Why not use it?
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-12-19 17:37 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
2019-12-19 16:03 ` Michał Górny
2019-12-19 17:28 ` Sebastian Pipping
2019-12-19 17:37 ` Michał Górny [this message]
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=fb46f0c2fc95f798e4b09005d8cb1ff185f62750.camel@gentoo.org \
--to=mgorny@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