On 29. 04. 19 15:42, Jared K. Smith wrote: > One of the frustrating things with NodeJS packaging in Fedora is that > because of the crazy number of dependencies between NodeJS packages, a > simple version bump in one package could cause a whole cascade of other > packages that need to be updated to newer versions to support that > dependency here.
That's why I'm only doing this in Rawhide (and I would love to have something akin to Rawhide-testing). > The right thing to do in this case is to look at each of those packages, > find anything that's dependent upon those packages, and make sure each > one will still work with the newer version of the package. That will never work (long-term) without the cooperation with the maintainers of the affected packages. I'm happy to help with any issues caused by the update, but I would leave finding these issues to koschei. Only other option I can think of is going the Rust route (packages only in rawhide, anything depending on them must be a module), which I'm not a fan of. Best regards, -- Jan Staněk Associate Software Engineer, Core Services Red Hat Czech jsta...@redhat.com IM: jstanek
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
