Hey Chris,
> That sounds sensible. On the specific name, given this is just about
> substitutes, and at least in my opinion has nothing to do with
> continuous integration, maybe picking just another word would avoid
> thinking too much, it could be bordeaux, or hippo, or anything
> really. As y
Ludovic Courtès writes:
> Hello!
>
> Christopher Baines skribis:
>
>> Christopher Baines writes:
>>
>>> Is there still a path to bring some of these benefits to users, and if
>>> so, what things need doing?
>
> [...]
>
>> Obviously just having the substitutes doesn't magically get them to
>> u
Hi,
Julien Lepiller skribis:
> I think the best way to bootstrap would be to reimplement Scala in another
> language. I tried that too, but even the parser is crazy.
Could you share a link to that so everyone realizes just how far you
went? :-)
That OCaml now has a clean bootstrapping story
Hello!
Christopher Baines skribis:
> Christopher Baines writes:
>
>> Is there still a path to bring some of these benefits to users, and if
>> so, what things need doing?
[...]
> Obviously just having the substitutes doesn't magically get them to
> users, so I've started looking in to the cha
I've rebuilt only up to python 3, and a handful pytgon packages, not a lot
more. I'm very confident for the one that enables optimisation, less so for the
one that removes files (supposedly useless, like windows binaries and test
files).
I'm go for both options, maybe python-update is more wise
Hi Erik,
There has been some work towards updating the OCaml packages in
Guix (see https://issues.guix.gnu.org/47768).
A lot of packages have been updated so that there is a now an
updated ocaml-X package for a previously existing ocaml4.07-X
package. This includes a lot of ppx'es. However n
Bonjour !
Julien Lepiller skribis:
> In the short term I'd like to merge the python optimisations. We
> discussed it before release and thought it might be nice to merge them
> before c-u, from a separate branch.
That’d be great!
BTW, another thing that’d be nice it to use Guile-Netlink to pro
Hi,
Bone Baboon skribis:
> 1) Make the core parts of Guix reproducible
>
> Many core parts of Guix are not reproducible. If more core parts of
> Guix were reproducible it would benefit all Guix users.
>
> There are several core parts of Guix that are not reproducible
> including:
>
> * Linux-li
Christopher Baines writes:
> Is there still a path to bring some of these benefits to users, and if
> so, what things need doing?
It's been a few weeks now, so to summarise, I think only one path
emerged, and that is to get substitutes from bayfront to users.
Bayfront was already running the G
On Sat, May 15, 2021 at 02:08:50PM -0400, Julien Lepiller wrote:
> In the short term I'd like to merge the python optimisations. We discussed it
> before release and thought it might be nice to merge them before c-u, from a
> separate branch.
+1
Have you tested them at all yet? If so, and they
Ludovic Courtès schreef op za 15-05-2021 om 19:47 [+0200]:
> [...]
> Here’s my wish list of things that look achievable within 4 to 6 months
> (I hope to help on some of these):
>
> • [...]
>
> • Merging ‘core-updates’, perhaps with a switch to GCC 10? Perhaps
> with support for “simplif
Bone Baboon writes:
> 1) Make the core parts of Guix reproducible
>
> Many core parts of Guix are not reproducible. If more core parts of
> Guix were reproducible it would benefit all Guix users.
>
> There are several core parts of Guix that are not reproducible
> including:
>
> * Linux-libre
>
El 18/5/21 a las 11:44, Ricardo Wurmus escribió:
Leo Prikler writes:
Hi Julien,
Am Dienstag, den 18.05.2021, 01:01 +0200 schrieb Julien Lepiller:
Hi Guix!
I have the attached file that build Scala, although it's not
bootstrapped at all. It contains %binary-scala, a few dependencies of
Scal
Hi, I have a project that requires a more recent core-kernel and some of
the ppx'es (such as ppx_fields_conv).
Being very new to guix I've managed to add/update packages for python
and ruby stuff, but this ocaml.scm file is quite different. There's a
lot going on which I'm guessing is related
Ludovic Courtès writes:
> So, now that 1.3.0 is out the door, what’s next?!
> What’s your wish list? What do you feel an urge to hack on? :-)
There are two improvements on my Guix wish list.
1) Make the core parts of Guix reproducible
** I do not know if this fits into the 4-6 month time frame
In the short term I'd like to merge the python optimisations. We discussed it
before release and thought it might be nice to merge them before c-u, from a
separate branch.
Maybe before next release we'll have our separate repo on savannah for
translations (it's currently a repo I manage on fram
I agree string freeze was way too long for this release. We entered string
freeze one week before the planned release date, it got pushed by almost one
month.
For next release, I think it would be better to enter string freeze along with
rc1 or a bit later, but always at least give one week bef
On Mon, May 17, 2021 at 10:35:22PM -0400, Joshua Branson wrote:
> I suppose someone should fix the Hurd vulnerabilities as reported here:
>
> https://lists.gnu.org/archive/html/bug-hurd/2021-05/msg00079.html
>
> I don't think the vulnerabilities have been disclosed yet nor has there
> been a fix
Am Dienstag, den 18.05.2021, 14:37 +0200 schrieb Julien Lepiller:
> Le Tue, 18 May 2021 13:36:43 +0200,
> Leo Prikler a écrit :
>
> > Am Dienstag, den 18.05.2021, 07:15 -0400 schrieb Julien Lepiller:
> > > The old scala is written in a superset of java5, that requires
> > > PiCo
> > > to build, a
Le Tue, 18 May 2021 13:36:43 +0200,
Leo Prikler a écrit :
> Am Dienstag, den 18.05.2021, 07:15 -0400 schrieb Julien Lepiller:
> > The old scala is written in a superset of java5, that requires PiCo
> > to build, and PiCo was built with JaCo. They were developped at
> > EPFL, and you can find a bi
Am Dienstag, den 18.05.2021, 07:15 -0400 schrieb Julien Lepiller:
> The old scala is written in a superset of java5, that requires PiCo
> to build, and PiCo was built with JaCo. They were developped at EPFL,
> and you can find a binary for it, but no source:
> http://zenger.org/jaco/
>
> Apparent
The old scala is written in a superset of java5, that requires PiCo to build,
and PiCo was built with JaCo. They were developped at EPFL, and you can find a
binary for it, but no source: http://zenger.org/jaco/
Apparently, JaCo was later reimplemented in Keris, whose source code is
available. H
Leo Prikler writes:
Hi Julien,
Am Dienstag, den 18.05.2021, 01:01 +0200 schrieb Julien
Lepiller:
Hi Guix!
I have the attached file that build Scala, although it's not
bootstrapped at all. It contains %binary-scala, a few
dependencies of
Scala we haven't packaged yet, and the final scala
Ludovic Courtès writes:
> Hi,
>
> Christopher Baines skribis:
>
>> If there's effort put in to getting substitutes served from bayfront,
>> why do you suggest not documenting how to get those substitutes in the
>> manual?
>
> Mostly because bayfront is not as powerful as the build farm behind
>
Hi Julien,
Am Dienstag, den 18.05.2021, 01:01 +0200 schrieb Julien Lepiller:
> Hi Guix!
>
> I have the attached file that build Scala, although it's not
> bootstrapped at all. It contains %binary-scala, a few dependencies of
> Scala we haven't packaged yet, and the final scala, built from
> %bina
25 matches
Mail list logo
