Hi,
On Thu, 8 Sept 2022 at 13:36, wrote:
> > srfi/srfi-1.scm:241:2: In procedure map:
> > In procedure map: Wrong type argument: "https://www.qt.io/";
> > building pages in '/tmp/gnu.org/software/guix'...
> >
>
> ISTM this "wrong type argument" is an infuriatingly common
On 08-09-2022 13:35, b...@bokr.com wrote:
Hi Simon, et al
On +2022-09-08 09:59:15 +0200, zimoun wrote:
Hi,
The website is currently failing [1] to build because a typo in some
package declaration. The error message is not very helpful,
srfi/srfi-1.scm:241:2: In procedure map:
On 08-09-2022 13:35, b...@bokr.com wrote:
Can geiser trace stuff? IWBN to have something analogous to bash's
shopt for printing expression sources as they are read and/or executed.
Does something like that exist?
See: 'trace' in the Guile manual. (This is a Guile feature, not a
geiser featur
On 08-09-2022 13:16, zimoun wrote:
Hi,
On Thu, 08 Sep 2022 at 11:32, Maxime Devos wrote:
On 08-09-2022 09:59, zimoun wrote:
We could add a lint checker. Is it a “good” idea?
We already have one, 'check-license'.
Yeah, but I was talking about check if the field return the expected
record t
Hi Simon, et al
On +2022-09-08 09:59:15 +0200, zimoun wrote:
> Hi,
>
> The website is currently failing [1] to build because a typo in some
> package declaration. The error message is not very helpful,
>
> srfi/srfi-1.scm:241:2: In procedure map:
> In procedure map: Wrong type a
Hi,
On Thu, 08 Sep 2022 at 11:32, Maxime Devos wrote:
> On 08-09-2022 09:59, zimoun wrote:
>> We could add a lint checker. Is it a “good” idea?
>
> We already have one, 'check-license'.
Yeah, but I was talking about check if the field return the expected
record type. Not only for the license
On 08-09-2022 03:17, jgart wrote:
Hi Maxime,
how does antioxidant build system for rust work at a high level?
https://notabug.org/maximed/cargoless-rust-experiments
all best,
There are two parts:
* The actual build system (antioxidant.scm) -- it reads the Cargo.toml
to see what the dep
On 08-09-2022 09:59, zimoun wrote:
We could add a lint checker. Is it a “good” idea?
We already have one, 'check-license'.
Because lint is not always applied, a check should be done when running
’make’ or a special target. Is it a “good” idea?
I suppose it is a possibility, but it adds a f
Hi,
The website is currently failing [1] to build because a typo in some
package declaration. The error message is not very helpful,
srfi/srfi-1.scm:241:2: In procedure map:
In procedure map: Wrong type argument: "https://www.qt.io/";
building pages in '/tmp/gnu.org/softw
Hi,
On Wed, 07 Sep 2022 at 17:18, jgart wrote:
> wdyt if we have the following option for `guix lint`?
>
> ```
> -f, --whole-file lint all the packages in the given file(s)
> ```
I would prefer -m/--manifest first. :-)
Cheers,
simon
10 matches
Mail list logo
