From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <ericbavier@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] scripts: add guix lint
Date: Tue, 22 Jul 2014 17:26:05 +0200 [thread overview]
Message-ID: <877g359zzm.fsf@gnu.org> (raw)
In-Reply-To: <87y4vlo47n.fsf@gmail.com> (Eric Bavier's message of "Tue, 22 Jul 2014 09:31:08 -0500")
Eric Bavier <ericbavier@gmail.com> 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 syntax errors that
> currently result in 'guix build' reporting something like "guix build:
> error: foo: unknown package".
Normally you get more details about that when typing ‘make’ (or C-c C-k
in Geiser.)
Detecting that would amount to doing the job of the compiler and module
system, basically.
Ludo’.
next prev parent reply other threads:[~2014-07-22 15:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 23:51 [PATCH 0/2] Add "guix lint" Cyril Roelandt
2014-07-21 23:51 ` [PATCH 1/2] scripts: add guix lint Cyril Roelandt
2014-07-22 9:03 ` Ludovic Courtès
2014-07-22 13:38 ` Ludovic Courtès
2014-07-22 14:31 ` Eric Bavier
2014-07-22 15:26 ` Ludovic Courtès [this message]
2014-08-25 1:52 ` [PATCH] " Cyril Roelandt
2014-08-25 22:44 ` Ludovic Courtès
2014-09-01 0:39 ` [PATCH 1/2] Move specification->package to gnu/packages.scm Cyril Roelandt
2014-09-01 0:39 ` [PATCH 2/2] scripts: add guix lint Cyril Roelandt
2014-09-01 21:19 ` Ludovic Courtès
2014-09-01 8:55 ` [PATCH 1/2] Move specification->package to gnu/packages.scm Ludovic Courtès
2014-07-21 23:51 ` [PATCH 2/2] gnu/packages: Remove trailing periods in some synopses Cyril Roelandt
2014-07-22 19:27 ` [PATCH 0/2] Add "guix lint" Andreas Enge
2014-07-22 20:25 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877g359zzm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ericbavier@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.