all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 33137@debbugs.gnu.org
Subject: bug#33137: [Wishlist] recursive guix lint
Date: Wed, 31 Oct 2018 11:57:38 +0200	[thread overview]
Message-ID: <20181031095738.GJ1297@macbook41> (raw)
In-Reply-To: <87sh0nz4ir.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

On Tue, Oct 30, 2018 at 07:13:48PM +0100, Ludovic Courtès wrote:
> Hello,
> 
> Efraim Flashner <efraim@flashner.co.il> skribis:
> 
> > I meant more like "hey, khard can be upgraded to 0.12.2, after I've
> > checked the upgrade with 'guix lint khard', now I'd like to check the rest
> > of the dependency tree with 'guix lint --recursive khard' to see if
> > anything else can be upgraded or has any linter errors."
> 
> Oh I see.  So to me this would be a ‘guix refresh’ feature rather than
> ‘guix lint’, but I agree it would be nice (and not too hard to
> implement.)
> 
I think ultimately implementing it in both would be good, but even just
having it for refresh would go a long way to shedding light on some of
our libraries that aren't updates as often as they might be. Especially
with the scripting langaguages.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-10-31  9:58 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
2018-10-30  7:35       ` Efraim Flashner
2018-10-30 18:13         ` Ludovic Courtès
2018-10-31  9:57           ` Efraim Flashner [this message]

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=20181031095738.GJ1297@macbook41 \
    --to=efraim@flashner.co.il \
    --cc=33137@debbugs.gnu.org \
    --cc=ludo@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.