Hello!
l...@gnu.org (Ludovic Courtès) skribis:
> We discussed some time ago the possibility to automatically instantiate
> services. Now that service types have default value, I think it’s a
> viable approach: if a service is required, and *if* it provides a
> default value, then we can automati
Leo Famulari writes:
> On Mon, Jan 01, 2018 at 06:12:49PM +0100, Ludovic Courtès wrote:
>> We’ll have to stay focused in the coming days to fix everything as
>> quickly as we can.
>
> The latest core-updates evaluation is coming together [0], but there are
> still a few notable issues:
>
> * Pand
On Sat, Jan 20, 2018 at 08:16:04PM +, Fis Trivial wrote:
> I am currently running guix on top of Fedora 26. This is a mix of several
> problems, and possibly contains bugs in guix, I am not sure if I have done
> anything wrong. So I will try to describe them in order. If you believe I
> should
Here are two patches that:
* Add gcc-7.3.0-RC-20180117, which includes support for retpoline.
* Use gcc-7.3 to build linux-libre on x86 systems.
I'm currently running linux-libre-4.14.14 with full retpoline support:
mhw@jojen ~$ cd /sys/devices/system/cpu/vulnerabilities
mhw@jojen /sys/devic
I am currently running guix on top of Fedora 26. This is a mix of several
problems, and possibly contains bugs in guix, I am not sure if I have done
anything wrong. So I will try to describe them in order. If you believe I
should make separate threads or fill a bug report, just tell me to.
I trie
Danny,
Danny Milosavljevic wrote on 20/01/18 at 11:40:
> We should change that in core-updates-next, if possible.
>
> I think that native-inputs shouldn't end up in the final binary as a
> reference [...]
This has been discussed before, and I agree. (I started a branch to do
so but it breaks qui
On Tue, 07 Nov 2017 14:39:53 +0100
l...@gnu.org (Ludovic Courtès) wrote:
> We could meet for the whole day, in a place that remains to be defined,
> to discuss about all things Guix{,SD}. The event could be a mixture of
> short talks on specific topics, discussions on technical and less
> technic
Hi Leo,
> Although native-inputs are typically things that are only required while
> building [0], there's nothing that prevents a built package from keeping
> references to native-inputs.
We should change that in core-updates-next, if possible.
I think that native-inputs shouldn't end up in th