Hi Folks,
Between the continuous improvements in speed, the high availability of
substitutes, the arrival of PostGIS, QGIS and Geary and now Gnome 3.34,
Python 3.8 and IceDove... it feels to me like Guix Christmas!
Guix System has been my primary OS for a year or two now, but in the
last few mont
d9i9kxc7ywfwwaz3zgs4z-jitsi-2.10.drv - 1
builder for `/gnu/store/hxpb6xvx324d9i9kxc7ywfwwaz3zgs4z-jitsi-2.10.drv' failed
to produce output path `/gnu/store/kz7kwgm25xk83fc69immm80dazv9gb6x-jitsi-2.10'
note: keeping build directory `/tmp/guix-build-jitsi-2.10.drv-0'
guix build: error:
Hi Julien, Thomas, Ludovic and Chris,
Thanks very much for your tips on my Jitsi building adventures from a
few weeks back! I’ll keep you posted on the progress.
Regards,
Ben
On Wed, 08 Nov 2017, julien lepiller wrote:
> Le 2017-11-08 05:01, Ben Sturmfels a écrit:
>> Hi Folks,
&
s I
can see the change in
/tmp/guix-build-postgis-2.4.2.drv-7/postgis-2.4.2/configure.ac, but it
seems that the corresponding "configure" file is unchanged, so I'm
obviously missing something.
Any thoughts on this or a better approach?
Regards,
Ben
Ben Sturmfels
Sturm Software En
Hi Ludo,
On Fri, 19 Jan 2018, Ludovic Courtès wrote:
> However, I’d recommend simply patching ‘configure’ itself in a snippet,
> using ‘substitute*’. That way, you won’t have to add these dependencies
> and extra phase.
Thanks, substitute* is much neater and changing configure directly is
worki
On 01/05/19 03:16, Dexter Morgan wrote:
>[9] Twinkle (https://directory.fsf.org/wiki/Twinkle)
Hi Dexter,
Twinkle is in Guix too - I use it every day and it works very well. For
what it's worth, I wouldn't recommend packaging Ekiga. I've tried it
many times on other operating systems over the
Hi Folks,
On the rare occasion I dip into Guix packaging, I rely on Pierre's
tutorial[1] because it has the least confusing definition of
"native-inputs" "inputs" and "propagated-inputs". Before that tutorial
existed, I don't think I properly understood the difference.
I know this is superficial,
On Tue, 23 Jul 2019, Ricardo Wurmus wrote:
> The difference between “native-inputs” and “inputs” is not about whether
> they are needed at build time or runtime. The difference only really
> comes into play when cross-building. “native-inputs” must be of the
> host architecture, while “inputs” a
Sorry, same as Robert, I've lost the original mail.
>> Ludovic Courtès writes:
>>
>> [...]
>>
>>> What do *you* want Guix to address in the future?
>>>
>>> #+TITLE: GNU Guix Beyond 1.0—A Road Map
I'd love to be able to annotate user and system generations with some
text, so that the text is show
