Source Repository Rules
By kto on Apr 13, 2009
A few commandments for dealing with Software repositories (source bases) and the build results of those repositories.
- There shalt not be binary files in the repository.
Binary files (executables, native libraries, zip files, jar files, etc.) are NOT source and should not be managed in a source repository.
- Keep thy path names simple.
Directory names and filenames in the repositories should never contain blanks or non-printing characters. Certain characters such as '$' should also be avoided.
- There shall be one newline convention.
The contents of all source files should follow the standard unix conventions on newlines (no \^M's).
- Generated source files shall not be added as managed files.
Source files generated during the build process should not be managed files in a repository.
- All output from the build shall be kept separated from the source.
All files generated during the build should land in a well defined output only directory such as build/ or dist/. The src/ directory should never get written to during the build process.
Of course the commandments will change from time to time.
Reminds me of this scene in Mel Brooks
"History of the World Part II"
movie, loved the ending "These 15 Commandments... oops... 10 Commandments!". ;\^)