Jan Nieuwenhuizen writes:
> Hmm, make check showed some silly errors, I needed this patch
And I needed another one to get tests/builders.scm to pass. And
although it passes it builds most of mes bootstrap in ./test-tmp, which
takes quite a bit of time.
Moreover, quite some other problems
=
On Fri, Sep 21, 2018 at 23:35:17 -0400, Mark H Weaver wrote:
> Thanks to your hard work on our Rust packages, I was able to update our
> IceCat package to a pre-release of 60.2.0. I recently pushed it to
> master and Hydra is currently busy bootstrapping the chain of Rust
> compilers in order to e
Hi Danny,
Danny Milosavljevic writes:
>> How would you feel about doing further Rust work on a separate branch,
>> and periodically (maybe 2-4 times per month) merging the collected
>> improvements into master?
>
> I agree actually. Rust is taking up way too much of my own build
> capacity righ
Ludovic Courtès writes:
Hi!
>> I finally realised what it really means that the GuixSD bootstrap has
>> `binutils-cross-boot0' (I really think that should be reflected in the
>> SCM name too?) and `gcc-cross-boot0': bolting the x86_64-linux bootstrap
>> onto the i686-linux Mes bootstrap proved to
Ludovic Courtès writes:
Hi Ludo',
> (And sorry for the delay; I reckon my mail scheduling algorithm leaves a
> lot to be desired…)
AFAICS, esp. what's coming your way you schedule way better than I do ;)
>> +@node Reduced Binary Seed Bootstrap
>> +@section The Reduced Binary Seed Bootstrap
>
>
Danny Milosavljevic writes:
> Hi Mark,
>
> On Fri, 21 Sep 2018 23:35:17 -0400
> Mark H Weaver wrote:
>
>
> If anyone wants a simple way to contribute to getting Rust bootstrapped,
> please provide some cpu time to help with compiling Rust :)
I've got a 4 year old AMD APU 4 core sitting at my pa
Pierre Neidhardt skribis:
> When outputting the result of a commandline search, it could be handy to
> add a field "Installed? [yes|no]".
FWIW I’m not very enthusiastic but not opposed either. :-)
Ludo’.
Hello Pierre,
Pierre Neidhardt skribis:
> What about adding an optional "tags" field to the package record?
>
> Tags would be arbitrary (e.g. "editor", "video", "music", etc.) and
> useful for package exploration, both from commandline and guix.el I
> suppose.
I have mixed feelings about this.
Hello Marius,
Marius Bakke skribis:
> I've set up a channel for Chromium here:
>
> https://gitlab.com/mbakke/guix-chromium
Nice! Great to see channels put to good use. :-)
Though… let’s make sure this channel doesn’t derail “us” from the goal
of having an FSDG-compliant Chromium in Guix prop
Hello Mark,
Mark H Weaver skribis:
> Anyway, the situation is that our MIPS port is more or less "on ice",
> meaning that it could be revived with modest effort, but at the present
> time there's not enough developer attention to keep it functional.
What do you think would be the best course of
Hello!
Jan Nieuwenhuizen skribis:
> Jan Nieuwenhuizen writes:
>
>> Just to give you a heads up: four `Oops' fixup-commits later I decided
>> to squash them again and create a fresh wip-bootstrap: d7feea557.
>>
>> I think it could be ready for a rename to core-updates-next.
>>
>> $ guix hash -r /
Hello!
(And sorry for the delay; I reckon my mail scheduling algorithm leaves a
lot to be desired…)
Jan Nieuwenhuizen skribis:
> Ludovic Courtès writes:
[...]
>> $ guix hash -r /gnu/store/58q6748dydqxrhrw8xn2gsf60djl6gvv-hello-2.10
>> 005zi21nvhmygjam6vsvkgmw9awsmyacz6a65naxcblrpbra1g94
>
> A
Hi Pjotr,
On Sat, 22 Sep 2018 09:11:42 +0200
Pjotr Prins wrote:
> On Fri, Sep 21, 2018 at 11:35:17PM -0400, Mark H Weaver wrote:
> > How would you feel about doing further Rust work on a separate branch,
> > and periodically (maybe 2-4 times per month) merging the collected
> > improvements into
Hi Mark,
On Fri, 21 Sep 2018 23:35:17 -0400
Mark H Weaver wrote:
> It took my fastest laptop about 36 hours to build the chain of 5 rust
> compilers required to get to the latest Rust release, and to build
> IceCat. By the time I had gotten IceCat built and tested, you had
> pushed a few more i
On Fri, Sep 21, 2018 at 11:35:17PM -0400, Mark H Weaver wrote:
> How would you feel about doing further Rust work on a separate branch,
> and periodically (maybe 2-4 times per month) merging the collected
> improvements into master?
Or have a stable package which is a good idea anyway, especially
15 matches
Mail list logo
