From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/31539] New: abidb: formalize solib metadata abeam abixml
Date: Sat, 23 Mar 2024 09:01:03 +0000 [thread overview]
Message-ID: <bug-31539-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31539
Bug ID: 31539
Summary: abidb: formalize solib metadata abeam abixml
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: unassigned at sourceware dot org
Reporter: fche at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
An abidb git repo stores primarily abixml documents. In order to allow a user
to more fully diagnose a problem, it'd be useful to also store some metadata
for the solibs, such as:
- the path name(s?) for the shared library (/lib64/libfoo.so.45)
- the package name from which the file was extracted (foo-libs.rpm)
- version tagging of the abidw binary
- abidw options in effect
Such bits could go into an optional file right beside the abixml file, with a
naming convention such as /path/buildid.json (or perhaps xml or txt :-).
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2024-03-23 9:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-31539-9487@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.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.
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).