Thanks Leo for the explanation. Now I understand why Go programs, such
as the IPFS implementation, have so many dependencies... What I
understand now is that packages get built 'lazily' and there is really
no way to force a build - other than running the target software. I
noticed the hash values
Hello Guix!
Videos of this summer’s GNU Hackers Meeting are on-line:
https://audio-video.gnu.org/video/ghm2017/
Thanks to Christopher Dimech and Luca Saiu for taking care of it!
Ludo’.
Hi Chris,
Christopher Allan Webber writes:
> Mark H Weaver writes:
>
>> Tobias Platen writes:
>>
>>> On 02.10.2017 20:52, Christopher Allan Webber wrote:
Since these don't provide Guix in the main repo (and Debian won't
because we
Hello Guix,
I don't know if anyone else has noticed, but it seems that our
sge-pygame package is failing to build because the package version on
PyPI has downgraded from 1.5.1 to 1.5. I'm not sure why this has
happened, as the recommended version on the SGE-Pygame website is still
1.5.1. This
Based on my work creating a go-build-system and packaging a non-trivial
Go application [0], I want to start a discussion on how we can
efficiently package Go software in Guix.
Go software is developed rather differently from most of what we
package, and I think our package abstraction does not
Hi all,
I recently mentioned Flatpak and Snap. There are GNOME Software
plugins for both of these formats [1][2] which makes them more
accessible to everyday users.
Does issue 17152 [3] mean that a matching plugin [4] is on the
Guix roadmap?
Could a plugin like this work on a system where Guix
Ricardo Wurmus writes:
> Christopher Allan Webber writes:
>
>> Since these don't provide Guix in the main repo (and Debian won't
>> because we violate the FHS with /gnu/) we could probably auto-generate
>> the .deb or .rpm from some gexp?
>
> I was thinking about adding
Mark H Weaver writes:
> Tobias Platen writes:
>
>> On 02.10.2017 20:52, Christopher Allan Webber wrote:
>>> Since these don't provide Guix in the main repo (and Debian won't
>>> because we violate the FHS with /gnu/) we could probably auto-generate
>>> the .deb or
Hi all,
Previous discussion suggested that Guix (the package manager)
could not be included in Debian (and therefore derivatives) due
to technical policy. As a Debian-derivative user (PureOS and
sometimes Ubuntu) I'd still like a convenient way to try out and
recommend Guix to others. That is,
> And I should add that we are committed to supporting Guix usage on other
> distros. This is an important use case.
Many thanks regarding this and other replies. I'll send follow up
questions in new threads.
Regards,
David
Christopher Allan Webber writes:
> Since these don't provide Guix in the main repo (and Debian won't
> because we violate the FHS with /gnu/) we could probably auto-generate
> the .deb or .rpm from some gexp?
I was thinking about adding support for the “deb” package
Tobias Platen writes:
> On 02.10.2017 20:52, Christopher Allan Webber wrote:
>> Since these don't provide Guix in the main repo (and Debian won't
>> because we violate the FHS with /gnu/) we could probably auto-generate
>> the .deb or .rpm from some gexp?
>>
>
Maxim Cournoyer writes:
>> Efraim Flashner writes:
>>
>>> On Fri, Sep 29, 2017 at 07:21:27PM +0800, Huang, Ying wrote:
[...]
>>> you're in need of a 'make clean'. If you don't want to have to rebuild
>>> everything, then 'rm -- gnu/*go
On 02.10.2017 20:52, Christopher Allan Webber wrote:
> ng0 writes:
>
>> Christopher Allan Webber transcribed 0.6K bytes:
>>> Konrad Hinsen writes:
>>>
On 02/10/2017 11:18, David Seaward wrote:
> To what extent is support for other distros a priority for the Guix
> project? In
On Sun, Sep 24, 2017 at 10:36:46AM +0200, Pjotr Prins wrote:
> followed by firing up a uxterm which I have as an alias
>
> alias guixterm='/home/wrk/.guix-profile/bin/uxterm -vb -fg black -bg
> lightyellow -fn *-fixed-*-*-*-*-20-*'
>
> guixterm &
>
> That gives me the full locale
15 matches
Mail list logo