GNU bug report logs - #33137
[Wishlist] recursive guix lint

Previous Next

To reply to this bug, email your comments to 33137 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: bug-guix <at> gnu.org
Subject: [Wishlist] recursive guix lint
Date: Wed, 24 Oct 2018 15:39:15 +0300

[Message part 1 (text/plain, inline)]

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.

-- 
Efraim Flashner   <efraim <at> 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

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 33137 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 33137 <at> debbugs.gnu.org
Subject: Re: bug#33137: [Wishlist] recursive guix lint
Date: Thu, 25 Oct 2018 15:31:32 +0200

Hello,

Efraim Flashner <efraim <at> 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’.

Message #11 received at 33137 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 33137 <at> debbugs.gnu.org
Subject: Re: bug#33137: [Wishlist] recursive guix lint
Date: Sat, 27 Oct 2018 23:30:13 +0300

[Message part 1 (text/plain, inline)]

On Thu, Oct 25, 2018 at 03:31:32PM +0200, Ludovic Courtès wrote:
> Hello,
> 
> Efraim Flashner <efraim <at> 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. 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.

-- 
Efraim Flashner   <efraim <at> 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

[signature.asc (application/pgp-signature, inline)]

Message #14 received at 33137 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 33137 <at> debbugs.gnu.org
Subject: Re: bug#33137: [Wishlist] recursive guix lint
Date: Sun, 28 Oct 2018 23:29:28 +0100

Efraim Flashner <efraim <at> flashner.co.il> skribis:

> On Thu, Oct 25, 2018 at 03:31:32PM +0200, Ludovic Courtès wrote:
>> Hello,
>> 
>> Efraim Flashner <efraim <at> 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’.

Message #17 received at 33137 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 33137 <at> debbugs.gnu.org
Subject: Re: bug#33137: [Wishlist] recursive guix lint
Date: Tue, 30 Oct 2018 09:35:29 +0200

[Message part 1 (text/plain, inline)]

On Sun, Oct 28, 2018 at 11:29:28PM +0100, Ludovic Courtès wrote:
> Efraim Flashner <efraim <at> flashner.co.il> skribis:
> 
> > On Thu, Oct 25, 2018 at 03:31:32PM +0200, Ludovic Courtès wrote:
> >> Hello,
> >> 
> >> Efraim Flashner <efraim <at> 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?
> 

I assume you mean 'guix lint -c refresh'. 'guix lint -c refresh foo' is
nice, but we don't have anything that could take the place of 'guix lint
-c refresh --recursive foo'

I just saw again 'guix refresh', 'guix refresh --recursive -m
my-manifest.scm' would be great.

> > 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?

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."

> 
> Thanks,
> Ludo’.

-- 
Efraim Flashner   <efraim <at> 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

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 33137 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 33137 <at> debbugs.gnu.org
Subject: Re: bug#33137: [Wishlist] recursive guix lint
Date: Tue, 30 Oct 2018 19:13:48 +0100

Hello,

Efraim Flashner <efraim <at> 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.)

Thanks,
Ludo.’

Message #23 received at 33137 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 33137 <at> debbugs.gnu.org
Subject: Re: bug#33137: [Wishlist] recursive guix lint
Date: Wed, 31 Oct 2018 11:57:38 +0200

[Message part 1 (text/plain, inline)]

On Tue, Oct 30, 2018 at 07:13:48PM +0100, Ludovic Courtès wrote:
> Hello,
> 
> Efraim Flashner <efraim <at> 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 <at> 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

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.