Hi,
since the Raspberry Pi open firmware effort has unstalled
https://github.com/librerpi/rpi-open-firmware/
I want to eventually package it in Guix.
It turns out that there are already config files for nix in the project above.
And we have a nix importer in Guix.
How do I use it
guix
Andreas Enge writes:
> And since we are on the bikeshedding front, I feel like writing a second
> message.
>
> On Fri, Oct 16, 2020 at 12:38:23PM +0200, Ludovic Courtès wrote:
>> As discussed on IRC recently, several of us think that using “#true” and
>> “#false” instead of “#t” and “#f”
Hi Ricardo,
On Tue, 20 Oct 2020 at 13:12, Ricardo Wurmus wrote:
> Comparison with EQ? is rarely useful in the context of Guix, because we
> usually don’t care about identity (“is the value behind this variable
> name and the value behind this other variable name one and the same,
> i.e. are the
Hi Danny,
Back to this. Since it would be nice to try to release (somewhere?)
an experimental guix Docker image.
On Thu, 24 Sep 2020 at 10:00, Danny Milosavljevic
wrote:
> Also, while doing that, using the guix binary 1.1.0 tarball from the website
> and
> issuing guix pull (ONLY), a lot of
And since we are on the bikeshedding front, I feel like writing a second
message.
On Fri, Oct 16, 2020 at 12:38:23PM +0200, Ludovic Courtès wrote:
> As discussed on IRC recently, several of us think that using “#true” and
> “#false” instead of “#t” and “#f” throughout or documentation and code
>
Hello,
on the bikeshedding front: I find #true and #false confusing, since
everything I see on the Scheme language seems to use #t and #f. My first
impression was that #true and #false were guilisms...
On Fri, Oct 16, 2020 at 03:36:06PM +0200, Tobias Geerinckx-Rice wrote:
> Maxim Cournoyer 写道：
>
Hello,
On Tue, Oct 20, 2020 at 02:45:54PM +0200, zimoun wrote:
> You are playing the devil's lawyer role, right?
> This is a question about the standard, right? It is not about #true
> or #false vs #t or #f.
> The Guile manual explains well, isn't it?
yes, indeed. What I want to say: Besides
Hi,
I'm experiencing export errors in Inkscape 1.0.1 on several formats like DXF or
Optimized SVG. I'm getting the following error:
```
Traceback (most recent call last):
File "output_scour.py", line 8, in
import inkex
File
zimoun 写道：
So 'define-syntax define-record-type*' needs to be fixed to
return
#true...
Not sure if this is a misunderstanding on my part or yours, but:
~ λ guile
scheme@(guile-user)> (define (return-#true) #true)
scheme@(guile-user)> (return-#true)
$3 = #t
Kind regards,
T G-R
Hi Andreas,
On Tue, 20 Oct 2020 at 12:33, Andreas Enge wrote:
> And since we are on the bikeshedding front, I feel like writing a second
> message.
You are playing the devil's lawyer role, right?
> On Fri, Oct 16, 2020 at 12:38:23PM +0200, Ludovic Courtès wrote:
> - The "non-typedness of
On Tue, 20 Oct 2020 at 14:59, Tobias Geerinckx-Rice wrote:
> zimoun 写道：
> > So 'define-syntax define-record-type*' needs to be fixed to
> > return
> > #true...
>
> Not sure if this is a misunderstanding on my part or yours, but:
>
> ~ λ guile
> scheme@(guile-user)> (define (return-#true) #true)
zimoun 写道：
Maybe it is on my part but it returns #t and not #true. So
somehow
you need to know that #t is also #true or fix the REPL to return
#true
and not #t.
Right. Making e.g. define-record-type ‘return #true’ would not
change what's actually returned under the hood.
(Thank
On Tue, 20 Oct 2020 at 15:32, Tobias Geerinckx-Rice wrote:
> zimoun 写道：
> > Maybe it is on my part but it returns #t and not #true. So
> > somehow
> > you need to know that #t is also #true or fix the REPL to return
> > #true
> > and not #t.
>
> Right. Making e.g. define-record-type ‘return
Hello, gentle maintainer.
This is a message from the Translation Project robot. (If you have
any questions, send them to .)
A new POT file for textual domain 'guix-manual' has been made available
to the language teams for translation. It is archived as:
Hello, gentle maintainer.
This is a message from the Translation Project robot. (If you have
any questions, send them to .)
A new POT file for textual domain 'guix' has been made available
to the language teams for translation. It is archived as:
On 20.10.2020 16:26, zimoun wrote:
On Tue, 20 Oct 2020 at 15:32, Tobias Geerinckx-Rice wrote:
zimoun 写道：
Maybe it is on my part but it returns #t and not #true. So
somehow
you need to know that #t is also #true or fix the REPL to return
#true
and not #t.
Right. Making e.g.
On Tue, 20 Oct 2020 12:53:58 +
Ekaitz Zarraga wrote:
> I'm experiencing export errors in Inkscape 1.0.1 on several formats
> like DXF or Optimized SVG. I'm getting the following error:
> I suppose it's because python-lxml package is not included in
> Inkscape. Is there any reason for that?
> For optimized SVG, the error is due to missing the package scour, which
> I meant to report, but was just reminded of because of your email.
>
> -
>
>
Hello, gentle maintainer.
This is a message from the Translation Project robot. (If you have
any questions, send them to .)
A new POT file for textual domain 'guix-packages' has been made available
to the language teams for translation. It is archived as:
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'guix' has been submitted
by the Spanish team of translators. The file is available at:
https://translationproject.org/latest/guix/es.po
(We can arrange things so that in
>
> Hey, everyone.
>> I wanted to share my progress with you. This last week I submitted my
>> first
>> patch ever. There were a few minor mistakes in it, so I had to fix them
>> and
>> submit again. It was a great opportunity for me to learn some new Git
>> commands -
>> like git rebase - and
Hi Ricardo,
Ricardo Wurmus writes:
> I think it’s very ugly that we still need to end phases with #T, even
> though build systems don’t care any more. The only thing that aborts a
> build phase now is an exception.
I would be glad if this were the case, but I believe you're mistaken.
On both
Bonface M. K. writes:
> Christopher Lemmer Webber
> writes:
>
> [...]
>
>>> Can I volunteer on this task? There's some work in
>>> my team done in Racket; and it would be of great
>>> interest to us to have a working Racket build
>>> system. I can set apart some time to work on
>>> this. I'd ask
23 matches
Mail list logo
