Re:GNU Guix 0.5 released
by peterwwillis on Friday December 13, 2013 @02:00PM
(#6902202)
Oh, I see what you mean about the source now - to make sure the binary I have is the direct product of only the developers' original code, or thereabout. This is what source packages (SRPMs) are for; you can download the SRPM, look at the code in it, and rebuild it if you're really paranoid. You can compare SHA hashes of the code you have with those of either the package builder or the original developers of the code. This requires no web of trust.
You don't need a declarative programming language to for your configuration management or your package management. It just makes for a maintenance headache. And using a dedicated CM tool like Puppet is a better idea because it makes the software more portable and flexible.
When you deploy your application, your package manager has to execute certain things in order to set it up for the first time. A CM can handle this, too. And once it's installed, you may need to change the configuration in a unified way. A CM handles this. At uninstall, your package manager cleans up after the package's setup, which a CM can also handle. By bundling these two, the application now only supports one system (the Nix system). If the software's configuration is completely handled by an independent CM tool like Puppet, it will be supported on any platform Puppet resides on, and because it's not tied to a single package manager you can install the software on any system.
I think the only way you're going to win the development war is to provide a portable, compatible, simple, maintainable, easy to use tool that everyone will want because it solves all of their problems without creating new ones. It can't be a programming language because most people can't program. It can't be complicated or overly powerful because most people will shoot themselves in the foot if you give them ammunition. And it has to work everywhere, on anything. Good luck!
You don't need a declarative programming language to for your configuration management or your package management. It just makes for a maintenance headache. And using a dedicated CM tool like Puppet is a better idea because it makes the software more portable and flexible.
When you deploy your application, your package manager has to execute certain things in order to set it up for the first time. A CM can handle this, too. And once it's installed, you may need to change the configuration in a unified way. A CM handles this. At uninstall, your package manager cleans up after the package's setup, which a CM can also handle. By bundling these two, the application now only supports one system (the Nix system). If the software's configuration is completely handled by an independent CM tool like Puppet, it will be supported on any platform Puppet resides on, and because it's not tied to a single package manager you can install the software on any system.
I think the only way you're going to win the development war is to provide a portable, compatible, simple, maintainable, easy to use tool that everyone will want because it solves all of their problems without creating new ones. It can't be a programming language because most people can't program. It can't be complicated or overly powerful because most people will shoot themselves in the foot if you give them ammunition. And it has to work everywhere, on anything. Good luck!