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

2024-08-10 Thread bluca at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #28 from Luca Boccassi --- As user and owner of the spec, I am fine with any of those options. A slight preference for a new command line (option A), as that means you don't need to worry about version matching - if the new flag is

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

2024-08-09 Thread bluca at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #26 from Luca Boccassi --- (In reply to Benjamin Drung from comment #25) > (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 repl

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

2024-08-09 Thread bluca at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #24 from Luca Boccassi --- (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) > > > > > > Will "%[string]" escape work? > > > > > > Like this?

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

2024-07-25 Thread bluca at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #21 from Luca Boccassi --- (In reply to Luca Boccassi from comment #10) > (In reply to H.J. Lu from comment #9) > > For non-working --package-metadata, we should either remove it or fix it. > > Sorry, but this is absolutely wrong,

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

2024-07-23 Thread bluca at debian dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=32003 --- Comment #10 from Luca Boccassi --- (In reply to H.J. Lu from comment #9) > For non-working --package-metadata, we should either remove it or fix it. Sorry, but this is absolutely wrong, as the existing option works just fine. I do not min