On Sun, Dec 15, 2024 at 03:15:11PM +0000, Peter Robinson wrote: [...] I'm a little surprised by Peter's email that he also has little insight into why this was done. But I have no reason to believe one person over another in this. I'll just say I've found Peter to be a very helpful and trusted packager in the past. > The problem with proven packager, and I have had it with my > packages, see note above about a rust SIG member and from other > people in this thread, is everyone wants things done done > differently, has their own preferred way of doing things, emails, > RHBZ, pull requests, etc, some are ignored, some sit for months > without action, others have outlined this in the thread as well. If > there was a way where people put a readme or something with details > I believe it would remove a LOT of the friction. [Or a comment in the spec file instead of a readme] Yes, I agree with Peter this is a real problem. If I'm updating the OCaml packages [as an example of something I'm planning to do soon] we really have to update and recompile them all in one go. It's not feasible to go through a months long asynchronous process where every package is a special flower. It's not a problem for OCaml packages since me & Jerry are de facto maintainers of all of them, but it's a problem for a small subset of the packages touched by RISC-V updates. I do think we need a bit less ownership and a bit more shared responsibility with packaging. For packages which I maintain, I'm happy for PPs to touch them without getting permission beforehand. Just try to do the right thing! Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com nbdkit - Flexible, fast NBD server with plugins https://gitlab.com/nbdkit/nbdkit -- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
