From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 33137@debbugs.gnu.org
Subject: bug#33137: [Wishlist] recursive guix lint
Date: Sun, 28 Oct 2018 23:29:28 +0100 [thread overview]
Message-ID: <878t2h66yf.fsf@gnu.org> (raw)
In-Reply-To: <20181027203013.GF1297@macbook41> (Efraim Flashner's message of "Sat, 27 Oct 2018 23:30:13 +0300")
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Thu, Oct 25, 2018 at 03:31:32PM +0200, Ludovic Courtès wrote:
>> Hello,
>>
>> Efraim Flashner <efraim@flashner.co.il> skribis:
>>
>> > We have the linter check for CVEs and updates to packages in a list, but
>> > what about those packages they depend on? It would be great to be able
>> > to 'guix lint --recursive foo' and get foo and also all the packages in
>> > the different types of inputs.
>>
>> On the question of CVEs, see also
>> <https://issues.guix.info/issue/31442>.
>>
>> Do you think --recursive would be useful for other types of linters?
>>
>> Thanks,
>> Ludo’.
>
> Checking for new versions would definately be good.
But that’s what ‘guix refresh’ does, right?
> It seems to me that checking everything would make for better code
> overall, but the behavior I would expect is that it would check all
> the linters specified in the command.
If you run ‘guix lint’ without any arguments, all the packages are
checked. Is this what you meant?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-10-28 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 12:39 bug#33137: [Wishlist] recursive guix lint Efraim Flashner
2018-10-25 13:31 ` Ludovic Courtès
2018-10-27 20:30 ` Efraim Flashner
2018-10-28 22:29 ` Ludovic Courtès [this message]
2018-10-30 7:35 ` Efraim Flashner
2018-10-30 18:13 ` Ludovic Courtès
2018-10-31 9:57 ` Efraim Flashner
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=878t2h66yf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33137@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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.