Re:Practical File System Design with the Be File System (199...
by wcummings on Friday April 24, 2015 @12:41PM
(#9434430)
Even if users don't need "Linux-style" package management, developers definitely do.
Re:Practical File System Design with the Be File System (199...
by teacup50 on Friday April 24, 2015 @03:08PM
(#9435423)
Only for "Linux-style" software, and it need not be built into the base system.
In fact, it should not -- if having a stable system on which binary software can be shipped is important, a built-in supported Linux-style dependency management system will undermine that goal entirely.
Re:Practical File System Design with the Be File System (199...
by yebyen on Friday April 24, 2015 @07:22PM
(#9436501)
I don't get "linux-style." It's not linux-style, it's "built-on-free-software" style. The other style is "I paid someone to do it" style. That's not really a style, it's just polar opposites.
Proprietary OS don't have that, which is why:
1) They can support stable binary-only commercial software, and
2) They do not need or benefit from Linux-style package management.
BeOS R5 had the stable APIs necessary to achieve a stable OS without Linux style package management. The shift away from that has also involved a shift away from the idea that the OS should ship ABI-stable libraries.
Linux-style package management isn't an appropriate tier-one feature for a modern stable desktop OS.