From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: 47479@debbugs.gnu.org
Subject: bug#47479: inkscape retains a reference to imagemagick, even though it is in native-inputs
Date: Tue, 30 Mar 2021 11:38:28 -0400 [thread overview]
Message-ID: <YGNF9O2KS+7hBwnV@jasmine.lan> (raw)
In-Reply-To: <8735wd2f77.fsf@netris.org>
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?
By the way, there is a new upstream release of the old series available,
0.92.5.
next prev parent reply other threads:[~2021-03-30 15:39 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 [this message]
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
[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=YGNF9O2KS+7hBwnV@jasmine.lan \
--to=leo@famulari.name \
--cc=47479@debbugs.gnu.org \
--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).