User talk: Cabryant
From LibrePlanet
m |
m |
||
| Line 26: | Line 26: | ||
* [http://nixos.org/~eelco/pubs/decvms-issre2010-final.pdf http://nixos.org/~eelco/pubs/decvms-issre2010-final.pdf] - Sander van der Burg, Eelco Dolstra. Automating System Tests Using Declarative Virtual Machines. | * [http://nixos.org/~eelco/pubs/decvms-issre2010-final.pdf http://nixos.org/~eelco/pubs/decvms-issre2010-final.pdf] - Sander van der Burg, Eelco Dolstra. Automating System Tests Using Declarative Virtual Machines. | ||
* [http://nixos.org/~eelco/pubs/clones-msr2011-final.pdf http://nixos.org/~eelco/pubs/clones-msr2011-final.pdf] - Armijn Hemel, Karl Trygve Kalleberg, Rob Vermaas, Eelco Dolstra. Finding Software License Violations Through Binary Code Clone Detection. | * [http://nixos.org/~eelco/pubs/clones-msr2011-final.pdf http://nixos.org/~eelco/pubs/clones-msr2011-final.pdf] - Armijn Hemel, Karl Trygve Kalleberg, Rob Vermaas, Eelco Dolstra. Finding Software License Violations Through Binary Code Clone Detection. | ||
| + | |||
| + | == Options for using Emacs Lisp to write SETI@home compatible programs == | ||
| + | |||
| + | * | ||
| + | * | ||
Revision as of 15:55, 17 May 2014
Why create a GNU OS on top of GNU Linux-libre source code build system?
Proposed reasons why it is needed:
- By building a very small collection of programs from source locally, you can be sure that everything compiled is doing what you expect it to do, having absolute control of your packages.
- A good build framework will analyze the code functionally, execute checksums, and validate that the licensing represents free software.
- Post-build, the framework will ideally execute a handful of tests to validate the system as a whole does what is expected of it.
- For such large builds (the GNU OS on top of a kernel) it makes sense to automate as much as possible, from checking code out of their source repositories, or downloading tarballs, to generation of configuration files (and version management of those).
Arguments against writing it:
- There are plenty of existing software configuration management options out there, many highly configurable and already rooted in the GNU environment, such as Guix.
Notes
- I may rewrite the arc build tool originally implemented in Scheme by Gregor Klinke in Emacs Lisp.
References:
- http://www.eyestep.org/arc.html - The Arc Build Tool Project, written in Scheme
- http://www.fsf.org/licensing/compliance - Free Software Foundation. License Violations and Compliance.
- http://www.gnu.org/philosophy/enforcing-gpl.html - Eben Moglen. Enforcing the GNU GPL.
- http://nixos.org/~eelco/pubs/phd-thesis.pdf - Eelco Dolstra. The Purely Functional Software Deployment Model.
- http://nixos.org/~eelco/pubs/hotos-final.pdf - Eelco Dolstra, Armijn Hemel. Purely Functional System Configuration Management.
- http://nixos.org/~eelco/pubs/iscsd-scm11-final.pdf - Eelco Dolstra. Integrating Software Construction and Software Deployment.
- http://nixos.org/~eelco/pubs/decvms-issre2010-final.pdf - Sander van der Burg, Eelco Dolstra. Automating System Tests Using Declarative Virtual Machines.
- http://nixos.org/~eelco/pubs/clones-msr2011-final.pdf - Armijn Hemel, Karl Trygve Kalleberg, Rob Vermaas, Eelco Dolstra. Finding Software License Violations Through Binary Code Clone Detection.
