unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Sent <richard@freakingpenguin.com>
To: MSavoritias <email@msavoritias.me>
Cc: 71700@debbugs.gnu.org, zimon.toutoune@gmail.com
Subject: bug#71700: The Archiving functionality of guix lint should be opt-in and Documented more prominently
Date: Sat, 22 Jun 2024 09:21:01 -0400	[thread overview]
Message-ID: <87iky1azb6.fsf@freakingpenguin.com> (raw)
In-Reply-To: <20240621194531.40c24620@fannys.me> (MSavoritias's message of "Fri, 21 Jun 2024 19:45:40 +0300")

I think channel level configuration of some form for code archival is a
good idea so individual channels can choose to disable it. I also agree
that we should make the fact that guix lint does archival more
prominent.

I disagree with a statement that permission is required, but I'll avoid
rehashing the discussion ongoing in guix-devel. [1]

I think there is a good reason to support disabling archival at the
channel level. Simon, do you think your patch can/will manage that?

> Somehow I disagree with this.  And I propose the generic approach that
> allows to exclude any checkers from the package definition using the
> field properties.
> 
> See <https://issues.guix.gnu.org/71697#1>.

[1]: https://lists.gnu.org/archive/html/guix-devel/2024-06/msg00192.html

-- 
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.




  parent reply	other threads:[~2024-06-22 13:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 16:45 bug#71700: The Archiving functionality of guix lint should be opt-in and Documented more prominently MSavoritias
2024-06-21 18:46 ` Simon Tournier
2024-06-22 13:21 ` Richard Sent [this message]
2024-06-22 14:24   ` Msavoritias
2024-06-22 15:30   ` Simon Tournier

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iky1azb6.fsf@freakingpenguin.com \
    --to=richard@freakingpenguin.com \
    --cc=71700@debbugs.gnu.org \
    --cc=email@msavoritias.me \
    --cc=zimon.toutoune@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).