From: "Ludovic Courtès" <ludo@gnu.org>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: 47230@debbugs.gnu.org
Subject: bug#47230: Build phase to graft during build for better grafts QA
Date: Thu, 18 Mar 2021 21:41:29 +0100 [thread overview]
Message-ID: <87lfakkxdy.fsf@gnu.org> (raw)
In-Reply-To: <618353059b4460b250ab12e0f556781e2ff07b56.camel@zaclys.net> ("Léo Le Bouter"'s message of "Thu, 18 Mar 2021 12:38:44 +0100")
Hi,
Léo Le Bouter <lle-bout@zaclys.net> skribis:
> I am having an hard time testing grafts in GNU Guix while I think we
> could have better tooling around this.
>
> For example, we could have a package transformation that can add a
> phase before 'check (or others) to graft any intermediate build binary
> and all dependencies (if not done already) to run the test suite WITH
> the graft. This could be turned on by GNU Guix contributors after
> trying to graft some package to ensure it does not break things.
>
> What do you think?
I think it’s more of a discussion for guix-devel than a bug report. :-)
What you describe, AIUI, is not possible: there are no phases or
anything like that happening on grafted packages. Quoth the manual
(info "(guix) Security Updates"):
Other restrictions may apply: for instance, when adding a graft to a
package providing a shared library, the original shared library and its
replacement must have the same ‘SONAME’ and be binary-compatible.
As I wrote earlier today, these things have to be checked by packagers;
they’re not easily automated because that usually involves knowing the
intent of upstream developers, for example whether they intend the new
version to be ABI-compatible with the version we have at hand, etc.
HTH!
Ludo’.
next prev parent reply other threads:[~2021-03-18 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 11:38 bug#47230: Build phase to graft during build for better grafts QA Léo Le Bouter via Bug reports for GNU Guix
2021-03-18 20:41 ` Ludovic Courtès [this message]
2021-03-19 9:44 ` Léo Le Bouter via Bug reports for GNU Guix
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=87lfakkxdy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=47230@debbugs.gnu.org \
--cc=lle-bout@zaclys.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 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).