6 ms·
Rules: 1. Use the system package manager. 2. See rule #1. In all seriousness, there needs to be a good way to [spray your stuff](http://dilbert.com/strip/201
by zdw 11y ago
Rules:
1. Use the system package manager.
2. See rule #1.
In all seriousness, there needs to be a good way to [spray your stuff](http://dilbert.com/strip/2013-06-09 http://dilbert.com/strip/2013-06-09) all over a system with the rest of the system knowing about it. FPM does a decent job of this.
There is some research out there on common things that this kind of code gets wrong: https://www.cs.arizona.edu/stork/packagemanagersecurity/ https://www.cs.arizona.edu/stork/packagemanagersecurity/
- snuxoll 11y agoThis is especially true with native code, between apt/yum/zypper/pacman on Linux and pacman as part of msys2 on Windows you really should be using your system package manager (if you need to, build your own packages, it really isn't that much harder than any of these language-specific ones, I swear).
- roel_v 11y agoThere was a tool I used years ago that would build rpm's from makefile-based build files. Basically, you would do './configure && make && [app name] make install' and it would then run a dummy 'make install', monitor syscalls that did copying etc. and make an rpm from that. That was easy enough to make packages from tarballs. Anything more complicated (like, having to actually know the package file formats) - forget it. Anyone know the name of this tool? It was unmaintained for a long time already when I stopped using Linux, and that was 10 years ago.
- hierro 11y agoI do remember using that tool to publish the very first aMule packages for Debian. I think it was called watchinstall.
- Sander_Marechal 11y agoIt's called `checkinstall`: https://wiki.debian.org/CheckInstall https://wiki.debian.org/CheckInstall
- roel_v 11y agoYeah that's the one, seems it's maintained after all. It was/is awesome.
- Zitrax 11y agoI used something similar named epkg, https://en.wikipedia.org/wiki/Encap_Package_Management_System https://en.wikipedia.org/wiki/Encap_Package_Management_Syste....
- snuxoll 11y agoIt was probably checkinstall, today I'd really recommend learning how to make an .rpm or .deb the proper way, it's really not that hard. My experience with debian packaging is fairly limited, but the typical rpmspec for a autotools based build is as simple as (minus package metadata because that's kinda noisy): %prep %setup -q %build %configure make %{?_smp_mflags} %install make install DESTDIR=%{buildroot} %files /usr/* Boom, there you go, build it with rpmbuild or mock and you're done. Debian control files are just Makefiles with a bunch of magic targets that get called, and debhelper 99% of the time will automatically figure out what you are trying to package (autotools, python, ruby, java, node, etc) and build/install/package it correctly for you so that most debian/control files are one or two lines.
- regularfry 11y agoYou only even need to go the debhelper route if you're intending your package to go upstream into Debian or Ubuntu itself. You can go a looooong way with just `DEBIAN/control` and `dpkg-deb --build`.
- spriggan3 11y ago> 1. Use the system package manager. When system package managers get properly documented maybe ... when instead of having 1 package manager per system , we have a single package manager for every system ... otherwise no, use the package manager that comes with the language if there is one.
- voltagex_ 11y agoWhich package manager are you running into trouble with?
- sergiosgc 11y ago> When system package managers get properly documented maybe Invalid complaint. The major package managers are extremely well documented. Even some of the minor ones, like archlinux.
- snuxoll 11y agoI don't think I'd call pacman minor anymore, it's pretty well known and is the package manager for msys2. slackware, on the other hand...
- pjmlp 11y agoThe day I am able to produce a package that will work in all OSes that I care, maybe. Until then, I surely will not waste my time generating one package per OS/distribution flavor.
- michaelmrose 11y agoSo 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?
- deleted 11y ago[deleted]
- curt15 11y agoDo any system package managers support per-user installations, or are they designed mainly to install to system directories? Pip for example has the option to install packages into the user's home directory, which allows for easy cleanup. If developers want to experiment with a library for a project, they might not want everything chucked into /usr/ and made part of the system.
- saulrh 11y agoThis is actually why I immediately discard use of the system package manager. One library version set per OS installation means that I can't run two things on the same machine unless I get really lucky with dependency versioning. Now the only way to get things done is to spin up one virtual machine per project, and completely setting up a new development environment per project is a huge pain in the ass that can only be optimized so far. nix/guix is a sort of reasonable answer to this issue, I guess, but then you have to develop on nix/guix and hope that apt/rpm/pacman can handle your dependencies.
- mordocai 11y agoAt least for guix, you can install it on top of any distribution and use it instead of the system package managers. I had some troubles with this when I did it, but nothing deal breaking and it isn't 1.0 yet so I imagine some of it will be cleaned up.
- gkya 11y agoFreeBSD ports and pkg allow you to set the installation base, with $LOCALBASE and $PREFIX (I guess other BSDs do too). Also AFAIK Guix. And BSD systems use /etc and /bin and /usr/bin for OS stuff, and /usr/local for packages. Even the config files go to /usr/local/bin/etc (NetBSD same, but in /usr/pkg).
- davexunit 11y agoGNU Guix[0] supports unprivileged package management, among other features [1]. Each user may maintain one or more "profiles" containing whichever packages they'd like. On top of that, they have access to a universal virtualenv-like tool called "guix environment"[2] that can create arbitrary software environments for development or even just to do one-off experiments. It can even create containers for maximal development environment purity. [0] https://gnu.org/s/guix https://gnu.org/s/guix [1] http://www.gnu.org/software/guix/manual/html_node/Features.html#Features http://www.gnu.org/software/guix/manual/html_node/Features.h... [2] http://www.gnu.org/software/guix/manual/html_node/Invoking-guix-environment.html#Invoking-guix-environment http://www.gnu.org/software/guix/manual/html_node/Invoking-g...
- davidgerard 11y agoAll software (not just languages) evolves until it contains a half-arsed rewrite of apt-get. You should be so lucky as to have a program package manner be at all compatible with apt or yum.