Andreas Enge skribis:
> This looks interesting, but similarly to some comment about "guix package
> --show", I am wondering about the profusion of commands.
I think --show may be useful to non-developers.
> Maybe we should use
>guix devel --lint
> instead? It would make clear that this opti
Hello,
On Fri, Jul 18, 2014 at 09:04:49AM +0200, Ludovic Courtès wrote:
> I’ve uploaded a new USB installation image for x86_64 for testing:
I just tried booting it, successfully, on my Dell Latitude (I think
E6320). As I have no free partition, I did not attempt an installation.
But guix command
On Tue, Jul 01, 2014 at 10:17:40AM +0200, Ludovic Courtès wrote:
> Maybe you could install Gettext with Guix? :-)
Yes, that was what I did already.
> Otherwise try lowering the version requirement, that may work.
But as I still think that it is good to keep guix bootstrapping from my
debian sta
This looks interesting, but similarly to some comment about "guix package
--show", I am wondering about the profusion of commands. Maybe we should use
guix devel --lint
instead? It would make clear that this option is only of interest to
developers, and pave the way for more developer related fu
While playing with standalone Guix, I found that I was unable to mount a
FAT-formatted USB drive. The kernel generated the following error message:
FAT-fs (sdb1): IO charset iso8859-1 not found
Loading the nls_iso8859_1 kernel module fixes the problem.
Isn't there normally some mechanism for
Commit a69576e mounts devtmpfs in a proper way.
Ludo’.
Eric Bavier skribis:
> Would it make sense to have 'guix lint' operate at the file/module level
> instead of at the package level?
You really mean at the syntactic level, no?
> That would be consistent with other lint-type tools, as far as I know.
> It would also, I think, help with things like
Ludovic Courtès writes:
> Cyril Roelandt skribis:
>
>> * guix/scripts/lint.scm: New file. Defines a 'lint' tool for Guix packages.
>> * Makefile.am (MODULES): Add it.
>
> This is nice!
>
> I think this should be modular so that, when possible, checkers can also
> be invoked at macro expansion ti
Two things I forgot to ask for (you’ll hate me for that ;-)):
1. Could you write tests for the checkers, as tests/lint.scm?
The tests would make sure that for a ‘package’ structure that
exposes the problem being checked for, the checker does emit a
warning on ‘guix-warning-port’,
Hello!
I’m completely ignorant here, but could it be that the system also
misses /dev nodes, as was reported yesterday by Adam?
Ludo’.
Taylan Ulrich Bayirli/Kammer (2014-07-22 10:53 +0400) wrote:
>> [...] get an object by its address (?), [...]
>
> (pointer->scm (make-pointer address))
>
> More info at (info "(guile) Foreign Variables").
>
> Warning: can lead to Scheme code that segfaults! :-)
>
> Taylan
Ludovic Courtès (2014-07
Cyril Roelandt skribis:
> * guix/scripts/lint.scm: New file. Defines a 'lint' tool for Guix packages.
> * Makefile.am (MODULES): Add it.
This is nice!
I think this should be modular so that, when possible, checkers can also
be invoked at macro expansion time. For instance, style checkers for
s
Taylan Ulrich Bayirli/Kammer skribis:
> Alex Kost writes:
>
>> [...] get an object by its address (?), [...]
>
> (pointer->scm (make-pointer address))
I was going to suggest that, but yeah, a vhash is more reasonable. :-)
Ludo’.
13 matches
Mail list logo