On 2019-04-29 10:31 a.m., Tom Hughes wrote: > On 29/04/2019 15:21, Jan Staněk wrote: > >> 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. > > Module don't work for Node.js though. > > They work for rust and go because of static linking, so different > packages can pull in the library versions (from parallel available > modules) at build time and then those libraries are statically > linked into the resulting program. > > Node.js is totally different though - there the node modules are > needed at run time by the installed packages not just at build time > so you would need parallel installability not just availability. Right. For major versions the only way is to resort to the good olde versioned packages. nodejs-xxx for the latest and nodejs-xxxN for the legacy one needed In the case of node I wonder if all packages should not be versioned with the major version anyway. Besides that, we'd have to relax dependencies with '^' around. But to do that we'd need to have some basic tests for the modules we meddle with the dependencies. Fernando > > Tom > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
