unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: librsvg & Rust
Date: Sat, 23 Mar 2019 17:53:06 +0100	[thread overview]
Message-ID: <87h8btwn0t.fsf@gnu.org> (raw)
In-Reply-To: <877ed09s0a.fsf@fastmail.com> (Marius Bakke's message of "Fri, 15 Mar 2019 14:39:01 +0100")

Hi!

Marius Bakke <mbakke@fastmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:

[...]

>>> 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))

It would have to be a macro so that the conditional is evaluated in a
context where (%current-system) and (%current-target-system) have the
right value, like the ‘glibc’ macro we had until commit
2d546858b139e5fcf2cbdf9958a17fd98803ac4c.

> Preferences?

I have a slight preference for having the same librsvg on all platforms.

So we could add 2.44 alongside 2.40, but keep using 2.40 until our Rust
package works on all the platforms.

That said, if the chances are that Rust won’t work on all 4 platforms in
the foreseeable future, the other option (upgrading on platforms where
Rust is supported) may be preferable.

Your call!  :-)

Thanks,
Ludo’.

  parent reply	other threads:[~2019-03-23 16:53 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   ` librsvg & Rust Ludovic Courtès
2019-03-06 15:46     ` 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 [this message]
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

  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=87h8btwn0t.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 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).