From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: gnu: imagemagick/fixed: Redirect old sonames to new sonames.
Date: Sat, 20 Mar 2021 16:26:13 -0400 [thread overview]
Message-ID: <87blbdlgfz.fsf@netris.org> (raw)
In-Reply-To: <YFY+zrvLa4aa6hbr@jasmine.lan>
Hi Leo,
> On Fri, Mar 19, 2021 at 08:14:03PM -0400, Mark H Weaver wrote:
>> The following dependency chain seems to be responsible for most of the
>> imagemagick-dependent packages:
>>
>> gtk+@3 -> at-spi2-atk -> at-spi2-core -> gtk-doc -> dblatex -> imagemagick
Leo Famulari <leo@famulari.name> writes:
> To clarify, the question is, what changed in the package dependency
> graph that caused so many packages to transitively depend on
> ImageMagick? Previously, we could update ImageMagick on the master
> branch.
I think you've answered your own question, below.
> Exploring the history of the dependency chain, using trusty `git log`:
>
> Dblatex was added in 2014, with a dependency on imagemagick.
>
> Gtk-doc was added in 2015, with a dependency on dblatex.
>
> at-spi2-core became dependent on gtk-doc in 2018. at-spi2-atk has
> depended on at-spi2-core since it was added 2013
>
> And gtk+ has depended on at-spi2-atk since 2013.
As you noted, at-spi2-core became dependent on gtk-doc in August 2018.
That's when the chain above was completed. My memory of 'imagemagick'
not having many dependents was from before then, I think.
Thanks for looking into it!
Mark
next prev parent reply other threads:[~2021-03-20 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 12:51 gnu: imagemagick/fixed: Redirect old sonames to new sonames Mark H Weaver
2021-03-18 13:08 ` zimoun
2021-03-18 13:40 ` Mark H Weaver
2021-03-18 19:44 ` Leo Famulari
2021-03-20 0:14 ` Mark H Weaver
2021-03-20 18:28 ` Leo Famulari
2021-03-20 20:26 ` Mark H Weaver [this message]
2021-03-27 9:36 ` Mark H Weaver
2021-03-27 18:06 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blbdlgfz.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).