From: Leo Famulari <leo@famulari.name>
To: Carl Dong <contact@carldong.me>
Cc: 46650@debbugs.gnu.org
Subject: bug#46650: Extending package transformation options
Date: Fri, 19 Feb 2021 19:17:40 -0500 [thread overview]
Message-ID: <YDBVJL/lDRIGLG3T@jasmine.lan> (raw)
In-Reply-To: <A993FD81-6D70-4834-A124-005BD2AD4E22@carldong.me>
On Fri, Feb 19, 2021 at 06:24:57PM -0500, Carl Dong wrote:
> One of the main reasons for switching over to Guix is for its bootstrappbility and the ability to perform `--bootstrap --no-substitutes` builds. As mentioned in the gnutls ticket, performing these source-based builds can sometimes reveal problems with tests suites:
> 1. Spurious tests
> 2. “Expiring” tests (like the gnutls one)
> 3. Foreign distro problems (0zmcam9sdiag9s1qx3xvlf8a3jnm53x2-sed-4.8.drv fails to build on SELinux-based distros because of a test failure in testsuite/inplace-selinux)
I hate to throw a wrench in your plans, but I think that using package
transformation options on the command-line militates against many of the
benefits you are seeking to take advantage of, in terms of an
introspectable and bootstrappable software system.
Normally when using Guix, our Git tree provides a convenient and
comprehensive view of the entire software system. It also provides an
entry point into the system for making changes.
When using these command-line package transformations, you diverge from
the Guix Git tree and enter uncharted and untracked territory. If you
install some software or build some system using these transformations,
there is no Git tree you can check out and begin exploring. For example,
there will be no package definition of GnuTLS-without-tests that can be
referred to and shared.
next prev parent reply other threads:[~2021-02-20 0:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 23:24 bug#46650: Extending package transformation options Carl Dong
2021-02-20 0:17 ` Leo Famulari [this message]
2021-02-20 14:00 ` Ludovic Courtès
2021-02-20 13:57 ` Ludovic Courtès
2021-02-23 22:22 ` zimoun
2021-02-24 11:11 ` Ludovic Courtès
2021-02-24 13:43 ` zimoun
2021-02-24 17:21 ` Ludovic Courtès
2021-02-26 21:44 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YDBVJL/lDRIGLG3T@jasmine.lan \
--to=leo@famulari.name \
--cc=46650@debbugs.gnu.org \
--cc=contact@carldong.me \
/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.