From: Rolf Eike Beer <eike@sf-mail.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Needs ideas: Upcoming circular dependency: expat <> CMake
Date: Thu, 19 Dec 2019 14:32:53 +0100 [thread overview]
Message-ID: <c9b3c0e9fb9d46973235431f10f6ff7f@sf-mail.de> (raw)
In-Reply-To: <CAD6zcDzJno4jbt9qSzZKEP1euXtGh9c_jhoVz3tiX69ULDzqVw@mail.gmail.com>
Am 2019-12-18 22:44, schrieb Francesco Riosa:
> Il giorno mer 18 dic 2019 alle ore 22:03 Sebastian Pipping
> <sping@gentoo.org>
> ha scritto:
>
>>
>> CMake bundles a (previously outdated and vulnerable) copy of expat so
>> I'm not sure if re-activating that bundle — say with a new use flag
>> "system-expat" — would be a good thing to resort to for breaking the
>> cycle, with regard to security in particular.
>>
> Pushing gently upstream to upgrade bundled expat copy would (at least
> temporarily) fix the issue and also benefit other use cases. Maybe they
> are
> Gentoo friendly
> they also release quite often, which would fix the problem soon
This is in CMake 3.16.0:
commit 50bc359184472700e9776a0a9d6f7e06ea82b9ce
Author: Brad King <brad.king@kitware.com>
Date: Mon Nov 11 10:44:17 2019 -0500
expat: Update CMake build for 2.2.9
commit b63a5c88a2089494e53f22f83db1925435161934
Merge: 512fabaa9d 1712885b4f
Author: Brad King <brad.king@kitware.com>
Date: Mon Nov 11 10:42:32 2019 -0500
Merge branch 'upstream-expat' into update-expat
* upstream-expat:
expat 2019-09-25 (a7bc26b6)
These things _are_ updated regularly, but in case something is missed
just file a bug at gitlab.kitware.com. All these bundled thing bumps are
scripted as far as possible, so the actual overhead is quite small.
Eike
next prev parent reply other threads:[~2019-12-19 13:40 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 [this message]
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
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=c9b3c0e9fb9d46973235431f10f6ff7f@sf-mail.de \
--to=eike@sf-mail.de \
--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