From: Marius Bakke <mbakke@fastmail.com>
To: Mark Wielaard <mark@klomp.org>, 38803@debbugs.gnu.org
Cc: Brett Gilio <brettg@gnu.org>
Subject: [bug#38803] [PATCH] gnu: elfutils: Update to 0.178
Date: Sun, 12 Jan 2020 21:54:52 +0100 [thread overview]
Message-ID: <87a76sxun7.fsf@devup.no> (raw)
In-Reply-To: <20200112203939.20141-1-mark@klomp.org>
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
Mark,
Mark Wielaard <mark@klomp.org> writes:
> This introduces debuginfod support which requires a couple of new inputs.
>
> * gnu/local.ml (dist_patch_DATA): Remove elfutils-tests-ptrace.patch.
> Add elfutils-0.178-tests-build-id.patch.
> * gnu/packages/elf.scm (elfutils): Update to 0.178
> [native-inputs]: Add iproute and pkg-config.
> [inputs]: Add cpio, libarchive, libmicrohttpd, libcurl, rpm and sqlite.
> [synopsis]: Updated.
> [description]: Updated.
> [license]: List all licenses used.
> * gnu/packages/patches/elfutils-tests-ptrace.patch: Removed. Fixed upstream.
> * gnu/packages/patches/elfutils-0.178-tests-build-id.patch: New. Patches
> backported from upstream git.
Thank you for these improvements. Could you submit the synopsis and
description update separately?
I worry about all the new inputs. This patch effectively makes us
unable to update all these inputs outside of the 'staging' or
'core-updates' cycles.
What is the difference in 'guix size elfutils' with and without this
patch?
Would it make sense to have a separate 'elfutils-minimal' for use in
Mesa, and expose the debuginfod-enabled variant as a separate package?
We could "hide" the minimal variant so that end users get the expected
package.
Also, for the patches, please add links to upstream commits in the patch
files, see some of the other patches for examples. I would also prefer
if they were separate files, seeing as the two commits do different
things.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-01-12 20:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 1:41 [bug#38803] [PATCH] gnu: elfutils: Update to 0.178 Mark Wielaard
2019-12-30 1:44 ` Brett Gilio
2019-12-30 2:04 ` Mark Wielaard
2020-01-12 20:39 ` Mark Wielaard
2020-01-12 20:54 ` Marius Bakke [this message]
2020-01-13 0:03 ` Mark Wielaard
2020-01-13 22:26 ` Marius Bakke
2020-01-31 12:43 ` Mark Wielaard
2020-01-31 15:49 ` Marius Bakke
2020-01-31 16:55 ` Mark Wielaard
2020-02-05 20:41 ` Marius Bakke
2020-02-06 11:04 ` Mark Wielaard
2020-02-06 11:36 ` Marius Bakke
2020-02-06 13:23 ` Mark Wielaard
2020-02-06 14:31 ` Marius Bakke
2023-09-02 18:39 ` Vagrant Cascadian
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=87a76sxun7.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=38803@debbugs.gnu.org \
--cc=brettg@gnu.org \
--cc=mark@klomp.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).