unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Graves via Guix-patches via <guix-patches@gnu.org>
To: 70416@debbugs.gnu.org
Cc: ngraves@ngraves.fr
Subject: [bug#70416] [PATCH 0/9] Remove uneeded python-pylint package in native-inputs.
Date: Tue, 16 Apr 2024 14:44:44 +0200	[thread overview]
Message-ID: <20240416125230.25265-1-ngraves@ngraves.fr> (raw)

Linters are often not really needed as native-inputs, as they are
often used for development but don't actually test package
functionality. Removing them when trivial is useful to lift some
unrequired dependencies, and slim a tiny bit the complexity of the
package graph.

This patch series will trigger a lot of rebuilds, so it should go to
the right branch (wip-python ?).

Nicolas Graves (9):
  gnu: python-fastjsonschema: Remove python-pylint native-input.
  gnu: python-trio: Remove python-pylint native-input.
  gnu: python-halo: Remove python-pylint native-input.
  gnu: python-log-symbols: Remove python-pylint native-input.
  gnu: python-spinners: Remove python-pylint native-input.
  gnu: tuir: Remove python-pylint native-input.
  gnu: rtv: Remove python-pylint native-input.
  gnu: python-clingraph: Remove python-pylint native-input.
  gnu: python-mediapy: Remove python-pylint native-input.

 gnu/packages/potassco.scm    | 2 +-
 gnu/packages/python-xyz.scm  | 3 ---
 gnu/packages/syndication.scm | 2 --
 gnu/packages/terminals.scm   | 7 +++----
 4 files changed, 4 insertions(+), 10 deletions(-)

-- 
2.41.0





             reply	other threads:[~2024-04-16 12:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 12:44 Nicolas Graves via Guix-patches via [this message]
2024-04-16 12:59 ` [bug#70416] [PATCH 1/9] gnu: python-fastjsonschema: Remove python-pylint native-input Nicolas Graves via Guix-patches via
2024-04-16 12:59   ` [bug#70416] [PATCH 2/9] gnu: python-trio: " Nicolas Graves via Guix-patches via
2024-04-16 12:59   ` [bug#70416] [PATCH 3/9] gnu: python-halo: " Nicolas Graves via Guix-patches via
2024-04-16 12:59   ` [bug#70416] [PATCH 4/9] gnu: python-log-symbols: " Nicolas Graves via Guix-patches via
2024-04-16 12:59   ` [bug#70416] [PATCH 5/9] gnu: python-spinners: " Nicolas Graves via Guix-patches via
2024-04-16 12:59   ` [bug#70416] [PATCH 6/9] gnu: tuir: " Nicolas Graves via Guix-patches via
2024-04-16 12:59   ` [bug#70416] [PATCH 7/9] gnu: rtv: " Nicolas Graves via Guix-patches via
2024-04-16 12:59   ` [bug#70416] [PATCH 8/9] gnu: python-clingraph: " Nicolas Graves via Guix-patches via
2024-04-16 12:59   ` [bug#70416] [PATCH 9/9] gnu: python-mediapy: " Nicolas Graves via Guix-patches via

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=20240416125230.25265-1-ngraves@ngraves.fr \
    --to=guix-patches@gnu.org \
    --cc=70416@debbugs.gnu.org \
    --cc=ngraves@ngraves.fr \
    /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).