Puritan/Principles: Difference between revisions
< Puritan
Jump to navigation
Jump to search
m (New page: Puritan is based on several fundamental principles. # Tools should be usable for both decentralized and centralized patterns of development. # People **will** want to make unpackaged ...) |
(Category:Build system redundant) |
||
| Line 9: | Line 9: | ||
# People working on the OLPC build system will become accustomed to [[git]] and [[python]]. |
# People working on the OLPC build system will become accustomed to [[git]] and [[python]]. |
||
[[Category:Build system]] |
|||
[[Category:Puritan]] |
[[Category:Puritan]] |
||
Latest revision as of 21:12, 27 August 2009
Puritan is based on several fundamental principles.
- Tools should be usable for both decentralized and centralized patterns of development.
- People **will** want to make unpackaged changes to their builds.
- Caching matters.
- Interactive development matters.
- Build reproducibility matters.
- Error-detection, handling, and cleanup matter.
- People working on the OLPC build system will become accustomed to git and python.