Quoting Jérémy Lal (2022-01-27 10:24:21) > Sometimes it's useful to be able to swap between nodejs debian package > and somewhat "official" https://deb.nodesource.com releases. > > Now that packages depend on nodejs:any, it's no longer possible to do > that, at least not without uninstalling many node-* modules.
That sounds like an interoperability bug in that unofficial nodejs package, not in this package. > Also i don't understand why debian packages would need to depend on > nodejs:any instead of plain nodejs. A fully multiarch-compatible system can contain packages compiled for multiple architectures installed side by side. E.g. an amd64 CPU can execute both amd64 code and i386 code - you can install a core amd64 system and choose to install an i386 nodejs. The nodejs runtime would only lookup arch-independent modules and modules for its own arch - modules compiled for i386 would need to depend on either native nodejs or foreign nodejs/i386 on a multiarch-system with nodejs/i386 installed. You can even mix binaries alien to the CPU - e.g. extend an ARM64 core system with MIPS binaries. Possibly they would then never really be used, or possibly (I haven't tried yet) you can install qemu and run emulated for those binaries. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
