public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Needs ideas: Upcoming circular dependency: expat <> CMake
Date: Wed, 18 Dec 2019 22:02:47 +0100	[thread overview]
Message-ID: <85c9df6f-fcf5-61d7-90af-a375f5c75088@gentoo.org> (raw)
In-Reply-To: <1a722f8f-36b5-c313-b6e1-eac75e0839c5@gentoo.org>

Hi all,


I noticed that dev-util/cmake depends on dev-libs/expat and that
libexpat upstream (where I'm involved) is in the process of
dropping GNU Autotools altogether in favor of CMake in the near future,
potentially the next release (without any known target release date).

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.

Do you have any ideas how to avoid a bad circular dependency issue for
our users in the future?  Are you aware of similar problems and
solutions from the past?

Thanks and best



Sebastian



       reply	other threads:[~2019-12-18 21:02 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 ` Sebastian Pipping [this message]
2019-12-18 21:08   ` [gentoo-dev] Needs ideas: Upcoming circular dependency: expat <> CMake 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
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=85c9df6f-fcf5-61d7-90af-a375f5c75088@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