Fabio Valentini wrote: > On Wed, Jan 22, 2025 at 10:52 AM Daniel P. Berrangé berrange@xxxxxxxxxx wrote: > > An increasingly large part of the ecosystem is working and deploying > > a way that Fedora (and derivative distros) are relegated to only > > delivering what's illustrated as Ring 1. This is especially the case > > in the CoreOS/SilverBlue spins, but we see it in traditional installs > > too which only install enough of Fedora to bootstrap the outside > > world. Meanwhile ring 2 is the space filled by either language specific > > tools (pip, cargo, rubygems, etc), and some docker container images, > > while ring 3 is the space filled by Flatpaks and further docker > > container images. Fedora meanwhile continues trying to package and > > deliver everything the same way as we did for decades, as if this > > shift were not happening. > > This kind of misses the point that Fedora packages do provide (in my > opinion) quite a lot of value on top of most language-specific package > package managers. > pip is a little bit more advanced than other tools here, but `go > install` and `cargo install` are extremely simplistic. > They download sources, build locally, and can only install executables > into the user's $PATH, nothing else. > The RPM package provides: > - no need to download sources and compile everything locally > (including installation of the Rust compiler, C compiler, > development headers for C libraries that are used, etc.) > - system-wide installation integrated with the package manager > - integrated installation of shell completions, manual pages, etc. - no need to download sources and compile everything locally - system-wide installation integrated with the package manager Are all of these true for libraries? I know that for C and C++ this is definitely true with integration via pkg-config, cmake being the closest analog and that nodejs, python and lua packages may need to do compiling or preprocessing for library packages but how does this hold up in other, especially statically compiled, languages? rust libraries are usually not compiled, don't need extra processing and I'm not sure if they ship any auxiliary files while rust applications don't automatically consume them unless crates.io is explicitly overwritten. zig libraries are essentially just copied into a folder, similar to rust though instead they are identified by a hash instead of their name and version number and zig applications only consume system libraries if `--system <path>` is specified during the build process. I'm not too well versed in go and the rpm macros for it are huge so I'm not sure how it deals with this. -- _______________________________________________ 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
