From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: librsvg & Rust Date: Fri, 15 Mar 2019 14:39:01 +0100 Message-ID: <877ed09s0a.fsf@fastmail.com> References: <20190220161027.17460.87383@vcs0.savannah.gnu.org> <20190220161038.3F54B2040C@vcs0.savannah.gnu.org> <87bm2ol0ud.fsf_-_@gnu.org> <875zswngzb.fsf@fastmail.com> <87y35g5qag.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:60361) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4n3M-0007XR-GM for guix-devel@gnu.org; Fri, 15 Mar 2019 09:39:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h4n3H-0001nP-UJ for guix-devel@gnu.org; Fri, 15 Mar 2019 09:39:13 -0400 In-Reply-To: <87y35g5qag.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: >>> 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? >> >> I have not noticed any regressions since the switch. The guile-rsvg >> tests pass, at least! > > One test would be to do =E2=80=98guix system vm-image --full-boot=E2=80= =99 or something, > to generate the derivation that builds the GRUB background image, which > uses Guile-RSVG. OK, good to know. The background image is fine (I'm using this branch on real hardware). >>> What do other distros do? Debian kept =E2=80=98librsvg-c=E2=80=99 arou= nd, primarily so >>> that architectures where Rust isn=E2=80=99t supported yet could still w= ork: >>> . >> >> I wanted to ask about this: is Rust supported on all the platforms we >> support at the moment? > > According to Efraim and Danny, we have a problem at the moment. > Presumably that can be worked around? Right, Rust currently only works on x86_64. In order to get this branch started, let us either: * Revert back to 2.40.20, or * Conditionally use the new version on supported platforms For the latter, I imagine something along the lines of... (define-public librsvg (if (string-prefix? "x86_64" (or (%current-target-system) (%current-system))) librsvg-2.44 librsvg-2.40)) Preferences? >> While depending on Rust for GTK/GNOME is unfortunate, I do think it's >> inevitable. > > Yeah. > >> By the way, the next version of librsvg will require Rust 1.33 or >> thereabouts. > > Oh so we=E2=80=99re lagging already? I was referring to the 2.46 series, but indeed 2.44.13 also fails with Rust 1.27 (we're at 2.44.12). --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlyLqvUACgkQoqBt8qM6 VPp18AgA0tYxflHSb60Wf9RRFtaGauj+QnvkJesTXiY/ZMbitR09SZ8PXYrloERS zk2o7RuOrTAPFGqa44OoyzIjo4L9cQpVdtNA6UFkkjz0QzJ/Vwg98fvaTqBzL+n4 iA9iEyUyExR1zOtRxbql7Yh6j71EzS1ZEe3vwBkHfrSyHyHhCMPisxViVPeRTdI6 zh9iPbDt+LehuEl52A4u3lKxmwTzuj8z0V0XeQs01FfjfdxWzYGtyl8Cr9ffs88m TfOMtR4x5udwfzIiX2qYLB8G3HV50CIOBcJfqVW7ZsrXLD+AFMAVtho9zkdv7Tth 2u3X4+oY+yT+0L6VuO4sKAEd2krC1w== =eyVf -----END PGP SIGNATURE----- --=-=-=--