From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: Mark H Weaver <mhw@netris.org>,
Efraim Flashner <efraim@flashner.co.il>,
47479-done@debbugs.gnu.org
Subject: bug#47479: inkscape retains a reference to imagemagick, even though it is in native-inputs
Date: Sun, 21 Jan 2024 20:15:02 -0500 [thread overview]
Message-ID: <87jzo26ueh.fsf@gmail.com> (raw)
In-Reply-To: <87czv7pkic.fsf@gmail.com> (Maxim Cournoyer's message of "Tue, 06 Apr 2021 10:15:07 -0400")
Hello,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Hi Leo et al.,
>
> Leo Famulari <leo@famulari.name> writes:
>
>> On Tue, Mar 30, 2021 at 04:55:13AM -0400, Mark H Weaver wrote:
>>> I see now that I'm using an older version, although I would have
>>> preferred the newer one. I refer to the variable name 'inkscape' from
>>> my manifest file, and I expected that to point to the latest stable
>>> version. However, it seems that one must use the 'inkscape-1.0'
>>> variable to get the latest stable version. That's seems suboptimal.
>>>
>>> I wonder if the 'inkscape' variable should be renamed 'inkscape/stable'
>>> (for use in packages such as 'dblatex/stable'), and then 'inkscape'
>>> could be repurposed to point to the latest stable version. Thoughts?
>>
>> I think we should do this, or even remove the old Inkscape package now.
>>
>> I'm guessing the reason for keeping the older release series is that
>> the Inkscape save-file format changed?
>
> The reason inksape@0.92 is still kept around is becauseInkscape@1
> doesn't build on ARM (more accurately, one of its dependencies,
> lib2geom, doesn't). It's been a while since I looked at the issue, and
> it seems there may have been some activity in lib2geom upstream to try
> to address the problem, so we should revisit it.
That's not relevant anymore, but our current inkscape 1.2 depends on
imagemagick still. Seeing how it now links directly to it, I've added
it to inputs as well in commit 552ebc47af and pushed to core-updates.
Closing!
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-01-22 1:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 16:33 bug#47479: inkscape retains a reference to imagemagick, even though it is in native-inputs Maxime Devos
2021-03-29 21:16 ` Mark H Weaver
2021-03-30 7:19 ` Efraim Flashner
2021-03-30 8:55 ` Mark H Weaver
2021-03-30 12:02 ` Efraim Flashner
2021-03-30 15:38 ` Leo Famulari
2021-03-30 22:48 ` Mark H Weaver
2021-03-31 5:30 ` Leo Famulari
2021-03-31 7:52 ` Mark H Weaver
2021-04-06 14:15 ` Maxim Cournoyer
2024-01-22 1:15 ` Maxim Cournoyer [this message]
[not found] ` <handler.47479.D47479.170588611628229.notifdone@debbugs.gnu.org>
2024-01-22 4:07 ` Maxim Cournoyer
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=87jzo26ueh.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=47479-done@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=leo@famulari.name \
--cc=mhw@netris.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.
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).