[Bug ld/32003] New: Specifying --package-metadata might not be possible and is too fragile

2024-07-22 Thread bdrung at posteo dot de
Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: bdrung at posteo dot de Target Milestone: --- In Ubuntu we enabled setting ELF package metadata for the Debian package that we build starting from Ubuntu 24.10

[Bug ld/32003] Specifying --package-metadata might not be possible and is too fragile

2024-07-22 Thread bdrung at posteo dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #1 from Benjamin Drung --- Proposed --encoded-package-metadata patches: * ld patch v4: https://sourceware.org/pipermail/binutils/2024-July/135769.html * gold patch v3: https://sourceware.org/pipermail/binutils/2024-July/135796.html

[Bug ld/32003] Specifying --package-metadata might not be possible and is too fragile

2024-07-23 Thread bdrung at posteo dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #6 from Benjamin Drung --- (In reply to H.J. Lu from comment #2) > > 2. The quotation marks in the JSON value are eaten by configure scripts and > > Makefiles. Example: > > > > ``` > > $ echo "void main() { }" > test.c > > $ print

[Bug ld/32003] Specifying --package-metadata might not be possible and is too fragile

2024-07-23 Thread bdrung at posteo dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #8 from Benjamin Drung --- (In reply to H.J. Lu from comment #7) > (In reply to Benjamin Drung from comment #6) > > > The encoding is flexible and you could just encode the characters that are > > problematic in your case: > > >

[Bug ld/32003] Specifying --package-metadata might not be possible and is too fragile

2024-07-23 Thread bdrung at posteo dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #11 from Benjamin Drung --- (In reply to H.J. Lu from comment #9) > It should be human readable. What do you recommend? IMO percent-escaping is readable enough and increases the size of the already long string not too much. The e

[Bug ld/32003] Specifying --package-metadata might not be possible and is too fragile

2024-07-23 Thread bdrung at posteo dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #13 from Benjamin Drung --- (In reply to H.J. Lu from comment #12) > (In reply to Benjamin Drung from comment #11) > > (In reply to H.J. Lu from comment #9) > > > It should be human readable. > > > > What do you recommend? IMO per

[Bug ld/32003] Specifying --package-metadata might not be possible and is too fragile

2024-08-09 Thread bdrung at posteo dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #23 from Benjamin Drung --- (In reply to H.J. Lu from comment #14) > (In reply to Benjamin Drung from comment #13) > > > > Will "%[string]" escape work? > > > > Like this? > > > > -Wl,--encoded-package-metadata={%[quot]type%[quo

[Bug ld/32003] Specifying --package-metadata might not be possible and is too fragile

2024-08-09 Thread bdrung at posteo dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #25 from Benjamin Drung --- (In reply to Luca Boccassi from comment #24) > (In reply to Benjamin Drung from comment #23) > > (In reply to H.J. Lu from comment #14) > > > (In reply to Benjamin Drung from comment #13) > > > > > > Wi

[Bug ld/32003] Specifying --package-metadata might not be possible and is too fragile

2024-08-09 Thread bdrung at posteo dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #27 from Benjamin Drung --- Taking all comments into account, here is my implementation proposals: Encoding schema === Option 1: Support percent-encoding of the JSON data. Percent-encoding is widely used and supported

[Bug ld/32003] Specifying --package-metadata might not be possible and is too fragile

2024-08-12 Thread bdrung at posteo dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #31 from Benjamin Drung --- (In reply to Andreas K. Huettel from comment #29) > > > > Option A: Introduce a new --encoded-package-metadata parameter that takes > > the encoded string. > > > > Option B: Extend --package-metadata t

[Bug ld/32003] Specifying --package-metadata might not be possible and is too fragile

2024-11-11 Thread bdrung at posteo dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #32 from Benjamin Drung --- >From the feedback so far here, I reworked the patches to implement variant 2B (support percent-encoding and %[string] encoding; extend --package-metadata to always decode the given string): * ld: https