From: "Léo Le Bouter via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 47230@debbugs.gnu.org
Subject: bug#47230: Build phase to graft during build for better grafts QA
Date: Fri, 19 Mar 2021 10:44:43 +0100 [thread overview]
Message-ID: <33efef8bb2595bb93282ae429d96d60bce28b413.camel@zaclys.net> (raw)
In-Reply-To: <87lfakkxdy.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]
On Thu, 2021-03-18 at 21:41 +0100, Ludovic Courtès wrote:
> I think it’s more of a discussion for guix-devel than a bug
> report. :-)
Yes but then I was thinking how do we track progress without losing it
in the pile of emails from guix-devel people receive everyday which
made me create a bug in the idea of "feature-request".. don't know.
> 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.
I am not sure we understand each other, I am proposing we could add
tooling to aid that testing.
> 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!
Yes of course, but aided by tooling that process can me smoother, e.g.
figuring out the SONAME has changed could at least be checked
automatically and issue a warning/error. Same thing with abidiff etc.
these tools are really great and we could create an easy way to run the
test suite of a package with the graft in also.
> Ludo’.
Thank you
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-03-19 9:46 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
2021-03-19 9:44 ` Léo Le Bouter via Bug reports for GNU Guix [this message]
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=33efef8bb2595bb93282ae429d96d60bce28b413.camel@zaclys.net \
--to=bug-guix@gnu.org \
--cc=47230@debbugs.gnu.org \
--cc=lle-bout@zaclys.net \
--cc=ludo@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).