From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Guix-devel <guix-devel@gnu.org>
Subject: native-inputs: Go for completeness or minimalism?
Date: Wed, 20 Jul 2022 10:33:54 +0200 [thread overview]
Message-ID: <54cc479c-8c7b-5161-0666-26ef199ef8b0@crazy-compilers.com> (raw)
Hi,
shall native-inputs be as complete as possible or as minimal as possible?
Background: I just stepped over a couple of packages where upstream
requires a lot of code-quality checkers which are not actually run when
running the tests. (More specific: These are Python packages demanding
tools like flake8, flake8-docstring, black, bandit.)
Now when going for minimal dependencies and minimal native-inputs,
Pro: Less dependencies, simpler dependency tree, thus less computation,
faster, less power consumption.
Con: Might need phase to remove dependencies, 'guix shell -D' will not
provide every development requirement.
Personally I tend to minimal.
WDYT?
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next reply other threads:[~2022-07-20 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 8:33 Hartmut Goebel [this message]
2022-07-20 9:03 ` native-inputs: Go for completeness or minimalism? Maxime Devos
2022-07-21 16:34 ` zimoun
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=54cc479c-8c7b-5161-0666-26ef199ef8b0@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@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 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).