all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 62062@debbugs.gnu.org
Subject: [bug#62062] [PATCH] guix: Strip #:use-module lists.
Date: Mon, 13 Mar 2023 15:19:26 +0100	[thread overview]
Message-ID: <87edps20pd.fsf_-_@gnu.org> (raw)
In-Reply-To: <87356eqrwq.fsf@cbaines.net> (Christopher Baines's message of "Thu, 09 Mar 2023 07:54:37 +0000")

Hi Chris,

Christopher Baines <mail@cbaines.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> This was obtained by setting up this environment:
>>
>>   guix shell -D guix --with-input=guile@3.0.9=guile-next \
>>     --with-commit=guile-next=e2ed33ef0445c867fe56c247054aa67e834861f2
>>     -- make -j5
>>
>> then adding 'unused-module' to (@@ (guix build compiler) %warnings),
>> building, and checking all the "unused module" warnings and removing
>> those that were definitely unused.
>
> This looks great :)
>
> It does change some guix/build/ modules though, so I think that is the
> reason it affects ~3227 packages. Maybe this could be split so that
> anything affecting packages goes to core-updates, and the rest of the
> changes go to master?

Sorry for being disorganized: I just saw this after pushing the patch.

Consequently, I reverted some of the guix/build changes in
0bb0eeddf647e5d56afd4517b12919a36acac6ee.

I’ll leave the rest for ‘core-updates’.

I should have checked data.qa.guix to see the number of rebuilds, right?

Thanks!

Ludo’.




  reply	other threads:[~2023-03-13 14:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 23:26 [bug#62062] [PATCH] guix: Strip #:use-module lists Ludovic Courtès
2023-03-09  7:54 ` Christopher Baines
2023-03-13 14:19   ` Ludovic Courtès [this message]
2023-03-09 10:25 ` Simon Tournier
2023-03-10  9:40   ` Ludovic Courtès
2023-03-10 11:37     ` Simon Tournier
2023-07-25 17:10 ` bug#62062: " Maxim Cournoyer

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=87edps20pd.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=62062@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    /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.