[blfs-dev] Policy on (not) updating rustc and cargo ?

Douglas R. Reno renodr2002 at gmail.com
Mon Apr 24 14:32:46 PDT 2017


On Mon, Apr 24, 2017 at 4:02 PM, Ken Moffat <zarniwhoop at ntlworld.com> wrote:

> On Mon, Apr 24, 2017 at 09:33:41AM +0200, balducci at units.it wrote:
> > > I agree.  Since rust and cargo are only used for FF (what about
> > > Thunderbird or Seamonkey?) then we should only consider updating
> > > rust/cargo when a new FF version is released.
> >
> > (sadly) rust/cargo seem to be required also for librsvg: devel version
> > 2.41.0 requires them and I guess they will be mandatory from stable
> > 2.42.x on...
> >
> >      https://github.com/GNOME/librsvg/blob/master/NEWS
> >
> >
> > ciao
> > -gabriele
>
> gabiele,
>
> thanks for that not-exactly-welcome news.  I suppose that in time
> other packages will also use it.  I've now created #9168 for rustc
> and cargo, with a status of hold.
>
> I just hope that the claims for added safety in rust turn out to be
> true.
>
>
Just as a heads up, I'm seeing more and more GNOME projects move to rust...
they had a hackfest in Mexico last week according to Christian Hergert
(@hergertme on twitter). He's one of the core GTK+ developers, and runs the
GNOME Builder IDE singlehandedly which is based directly off of rust.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfromscratch.org/pipermail/blfs-dev/attachments/20170424/31b33d50/attachment.html>


More information about the blfs-dev mailing list