From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel@gnu.org, Marius Bakke <mbakke@fastmail.com>
Subject: librsvg & Rust
Date: Wed, 06 Mar 2019 12:05:30 +0100 [thread overview]
Message-ID: <87bm2ol0ud.fsf_-_@gnu.org> (raw)
In-Reply-To: <20190220161038.3F54B2040C@vcs0.savannah.gnu.org> (guix-commits's message of "Wed, 20 Feb 2019 11:10:38 -0500 (EST)")
Hello Guix!
guix-commits@gnu.org skribis:
> mbakke pushed a commit to branch staging
> in repository guix.
>
> commit ec47c07d0690653be35a75b346f3c3548a3e71d4
> Author: Marius Bakke <mbakke@fastmail.com>
> Date: Wed Oct 24 15:26:10 2018 +0200
>
> gnu: librsvg: Update to 2.44.12.
>
> * gnu/packages/gnome.scm (librsvg): Update to 2.44.12.
> [arguments]: Replace patching phases with custom variants. Delete five new
> tests.
> [native-inputs]: Add RUST-1.27 and RUST-1.27:CARGO.
This change was bound to happen since upstream switched to Rust, but
it creates a few issues.
First, that adds Rust to the base graphical applications, which
significantly increases build times and size:
--8<---------------cut here---------------start------------->8---
$ guix size librsvg | tail -1
total: 207.2 MiB
$ guix size librsvg rust | tail -1
total: 1052.9 MiB
--8<---------------cut here---------------end--------------->8---
Perhaps the size issue can be somewhat mitigated by adding a “lib”
output to the Rust package, but even then it would probably still be an
issue.
Also, is the new librsvg API-compatible with the old one? IIUC it still
provides a C API, right? Does guile-rsvg still work, for example?
What do other distros do? Debian kept ‘librsvg-c’ around, primarily so
that architectures where Rust isn’t supported yet could still work:
<https://lwn.net/Articles/771355/>.
Anyway, lots of questions!
Thanks,
Ludo’.
next parent reply other threads:[~2019-03-06 11:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190220161027.17460.87383@vcs0.savannah.gnu.org>
[not found] ` <20190220161038.3F54B2040C@vcs0.savannah.gnu.org>
2019-03-06 11:05 ` Ludovic Courtès [this message]
2019-03-06 15:46 ` librsvg & Rust Marius Bakke
2019-03-06 16:24 ` ng0
2019-03-06 23:55 ` Mark H Weaver
2019-03-07 20:12 ` Efraim Flashner
2019-03-08 1:52 ` Danny Milosavljevic
2019-03-08 2:17 ` Danny Milosavljevic
2019-03-15 11:27 ` Ludovic Courtès
2019-03-15 11:29 ` Ludovic Courtès
2019-03-15 13:39 ` Marius Bakke
2019-03-15 15:14 ` Ivan Petkov
2019-03-23 16:53 ` Ludovic Courtès
2019-03-23 22:44 ` Marius Bakke
2019-04-03 21:30 ` Ludovic Courtès
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=87bm2ol0ud.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.