On Fri, Feb 05, 2021 at 10:07:33AM -0500, Matthew Miller wrote: > On Fri, Feb 05, 2021 at 03:55:33PM +0100, Frédéric Pierret wrote: > > >be doing it all the time. It's a perfectly good situation to _not_ optimize. > > > > That was my original remark that pulling a "big" RPM for just one file is > > not optimal. But as you said, it will probably concern very few amount of > > users. So inserting a buildinfo file into debuginfo RPM is a good start. > > Also, nothing is written in the stone? If needed in a future, we could > > change that. > > Yeah, exactly — we can optimize later. Sounds like a nice idea, but we only make debuginfo packages for packages that have debug symbols to strip out. Where would we put it for all the packages that don't have debuginfo now? Just make one? Thats could be a bit confusing. (why does this noarch script have a debuginfo file)? I think it might be better to do a new buildinfo subpackage, but just never distribute it (for now it just exists in koji/local builds). Then, once it someday becomes of use we could start shipping it somehow. But all this is getting a bit ahead. Someone needs to come up with the contents and tools to make/read/do cool things with them first. :) kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
