Re: 02/02: gexp: Default to current target.

[Mathieu Othacehe]

Hey,

> Could you push to ‘master’ as well?
>
> In general, to minimize the risks of merge conflicts, I’m all for
> pushing things on ‘master’ only (unless they entail full rebuilds of
> course.)  Eventually, they get merged to ‘core-updates’, ‘staging’, etc.

Yes makes sense! Pushed to master!

Mathieu

Re: 02/02: gexp: Default to current target.

[Ludovic Courtès]

Hi Mathieu,

guix-comm...@gnu.org skribis:

> mothacehe pushed a commit to branch core-updates
> in repository guix.
>
> commit a6bf7a9745f39afca7412f6627d24dc42ebf8075
> Author: Mathieu Othacehe 
> AuthorDate: Fri Mar 6 10:06:54 2020 +0100
>
> gexp: Default to current target.
> 
> * guix/gexp.scm (lower-object): Set target argument to 'current by 
> default and
> look for the current target system at bind time if needed,
> (gexp->file): ditto,
> (gexp->script): ditto,
> (lower-gexp): make sure lowered extensions are not cross-compiled.
> 
> * tests/gexp.scm: Add cross-compilation test-cases for gexp->script and
> gexp->file with a target passed explicitely and with a default target.

Could you push to ‘master’ as well?

In general, to minimize the risks of merge conflicts, I’m all for
pushing things on ‘master’ only (unless they entail full rebuilds of
course.)  Eventually, they get merged to ‘core-updates’, ‘staging’, etc.

Thanks,
Ludo’.