4 ms·
And then every package comes with its own libraries, which don't get updated and end up with duplicates everywhere. It's the same reason that Linux (the kernel)
by yjftsjthsd-h 8y ago
And then every package comes with its own libraries, which don't get updated and end up with duplicates everywhere. It's the same reason that Linux (the kernel) emphatically refuses to support out of tree drivers. It means that you have to make the effort to package it, yes, but once you've done that you get dependencies essentially for free. And as the end-user, I can update EVERYTHING on my system with one command, rather than the Windows hell of a dozen updaters running in the background constantly.
- AnIdiotOnTheNet 8y ago> And then every package comes with its own libraries Only if they aren't part of the base OS set. This is how basically every operating system except BSD and Linux do things, and they have an order of magnitude more adoption than the Linux Desktop. Hell Android even uses the Linux kernel and has an appstore and still does that. > It's the same reason that Linux (the kernel) emphatically refuses to support out of tree drivers. Well no, that's because they insist that drivers can be better maintained (because it forces them to be open) and don't have to tie their hands supporting an ABI. As an example of the downside of this policy, see nVidia drivers on Linux. Yes, it's a tradeoff, but there are a lot of downsides to package management that its proponents completely ignore. Case in point: the prevalence of using containers to run software without having to deal with conflicts created by trying to intermingle everyone's dependencies, or install up to date software without having to go through some repo, or distributing for multiple distros without having to maintain packages in two dozen repositories. Even Linus distributes with AppImage. Probably just a stupid Windows user.
- Annatar 8y ago"Case in point: the prevalence of using containers to run software without having to deal with conflicts created by trying to intermingle everyone's dependencies," That's a problem on GNU/Linux; it's not a problem on illumos or BSD based operating systems. Don't use GNU/Linux or package 3rd party and unbundled software in /opt, configuration in /etc/opt and configure the software to use /var/opt (as per the FHS specification) and the problem goes away. It's the clueless developer problem, not an OS packaging problem.
- AnIdiotOnTheNet 8y agoMaybe for that particular problem, it still doesn't do anything for many others. For instance, what if I want to install an application on a different disk? In grand UNIX tradition, the scheme you outlined still spreads an application's files all over the tree. I suppose you'll call that a packaging problem too, and I agree: you should package applications as relocatable directories that contain all their non-OS-provided dependencies.
- Annatar 8y ago"still spreads an application's files all over the tree" No, only three directories: /opt for application, /etc/opt for configuration, and /var/opt for applications' data. Please read the specification, either FHS[1] or AT&T original[2] from whence FHS came. Good engineers seek out and read specifications before they start any planning and work. When you package applications in this way, only /var/opt needs to be backed up. [1] http://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html http://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html [2] https://smartos.org/man/5/filesystem https://smartos.org/man/5/filesystem
- AnIdiotOnTheNet 8y agoRight, so instead of your entire application being in one directory, it is in fact spread across 3 disparate ones. Why not /opt/<APP>/(var|etc)? Would make too much sense I guess. I've read the spec, it's crap. There is no value to following a crap spec.
- Annatar 8y agoYou might have read it, but you didn’t understand it, and the reason you didn’t understand it is because you don’t understand the concepts behind UNIX. No matter; here is your next stop: “The art of UNIX programming” ...punch that into a search engine, read the book. Then we shall continue.
- 8y ago