4 ms·
So you are developing a package in language and you package it with insert language specific package manager you are now done. If you package it for insert sys
by michaelmrose 11y ago
So you are developing a package in language and you package it with insert language specific package manager you are now done. If you package it for insert system package manager to achieve a similar level of coverage you must not only figure out how to create packages for 17 different systems you have to either figure out the standards and procedures required to get your package included on each platform or figure out how to host your own repo and instruct users on how to set it up this may include variations in setup and instructions that differ between multiple versions of the os that may be in use concurrently.
This could be 1000 x as much work for not much gain.
- throwaway7767 11y agoRight, much more work for little gain for the developer. Then you have a bunch of developers all taking the easy way. And now all the system administrators running systems with those projects can't trust their packaging tools anymore, and have to do a lot more work in their daily workflow. Oh, and as a bonus, none of these systems have a secure update mechanism, so you've bypassed the inherent code whitelisting that comes with a system package manager with a centralised repository and a requirement for strong package signatures. At best, they do like PyPi and optionally allow a developer to specify a GPG key. So you have to do "pip install <bla>" and pray to the computer god that the developer of <bla> and all the developers of all its dependencies cared about code integrity and set up GPG keys. From experience, the chances of that are approximately 0%, because it's not a requirement.
- sergiosgc 11y ago> So you are developing a package in language and you package it with insert language specific package manager you are now done. No you are not. At this point, you have catered for developers in the language. You have not yet catered for final users. Really, the Linux landscape is not that scattered. Package for Debian and Redhat and you have done the Pareto effort.
- realityking 11y agoWhat about OS X? Windows? iOS? Android?
- NoGravitas 11y agoIdeally, your language package manager should know how to build (candidate) packages for common system package managers (eg '''setup.py bdist_rpm''' or '''setup.py bdist_debian'''). That way, the technical end user can install the package in a way their package manager knows about. If your package becomes widely used, it also simplifies (but does not remove) the job of the distribution's packager to build an official package. This doesn't work so well for micro-dependencies, though. The TeTeX distrib. in Fedora is bad enough, I'd hate to see the same done with node packages.
- emidln 11y agoThis isn't really usable if you develop with the latest packages for dependencies. While I could generate an rpm for my python module, Fedora and CentOS/RHEL are going to have incompatible dependencies. I could package up my dependencies too, but then I'll break system software (a lot of fedora's tooling is written in Python). A much better solution would involve making languages like Python accept the Python version as a dependency while making building the PYTHONPATH more flexible with common tooling. Making PYTHONPATH building better would enable installation with namespace+version, such that we could have: /usr/lib/pymodules/requests/1.0.0/... /usr/lib/pymodules/requests/1.2.1/... /usr/lib/pymodules/python/2.7.10/... /usr/lib/pymodules/python/3.5.0/... Python in particular is still a bit challenging in that the compiler assumes it can spit out byte-compiled code all over the place (.pyc), but if someone was going through the tooling effort, they'd presumably find a way (or get something merged if it doesn't exist), to add a shadow directory of .pyc files that could be keyed by version and cached somewhere user-writeable (~/.pymodules for example).
- talideon 11y agoThe purpose of PEP 3147 is to fix some of those problems: https://www.python.org/dev/peps/pep-3147/ https://www.python.org/dev/peps/pep-3147/ Addendum: I'd might as well mention that PEP 3147 is implemented from Python 3.2 onwards, so for Python 3, some of the problem is solved. You still have the issue of being able to install different version of the same library.
- Frondo 11y agoOr use CMake! CMake does this! https://cmake.org/Wiki/CMake:Packaging_With_CPack https://cmake.org/Wiki/CMake:Packaging_With_CPack