summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorSteven Knight <knight@baldmt.com>2002-12-05 16:43:51 (GMT)
committerSteven Knight <knight@baldmt.com>2002-12-05 16:43:51 (GMT)
commitcbf751b2a58f446e7a6a4230c918c4816710b3fa (patch)
tree923ed2c9febed74f13000d7b2f52d206a3ad7c82 /README
parent1989e2672394227e183691f93c012881ab371179 (diff)
downloadSCons-cbf751b2a58f446e7a6a4230c918c4816710b3fa.zip
SCons-cbf751b2a58f446e7a6a4230c918c4816710b3fa.tar.gz
SCons-cbf751b2a58f446e7a6a4230c918c4816710b3fa.tar.bz2
Prepare the 0.09 release.
Diffstat (limited to 'README')
-rw-r--r--README26
1 files changed, 20 insertions, 6 deletions
diff --git a/README b/README
index aa20969..13888aa 100644
--- a/README
+++ b/README
@@ -279,9 +279,21 @@ LICENSE
A copy of the copyright and terms under which SCons is
distributed (the Open Source Initiative-approved MIT license).
+LICENSE-local
+ A copy of the copyright and terms under which SCons is
+ distributed for inclusion in the scons-local-{version} packages.
+ This is the same as LICENSE with a preamble that specifies
+ the licensing terms are for SCons itself, not any other
+ package that includes SCons.
+
README
What you're looking at right now.
+README-local
+ A README file for inclusion in the scons-local-{version}
+ packages. Similar to this file, but stripped down and modified
+ for people looking at including SCons in their shipped software.
+
rpm/
The .spec file for building our RPM packages.
@@ -295,12 +307,14 @@ runtest.py
SConstruct
The "Makefile" for the SCons distribution.
- (It has been pointed out that it's hard to find the SCons API in
- this SConstruct file, and that it looks a lot more like a pure
- Python script than a build configuration file. That's mainly
- because all of the magick we have to perform to deal with all of
- the different packaging formats requires a lot of pure Python
- manipulation.)
+ (It has been pointed out that it's hard to find the SCons API
+ in this SConstruct file, and that it looks a lot more like a
+ pure Python script than a build configuration file. That's
+ mainly because all of the magick we have to perform to deal with
+ all of the different packaging formats requires a lot of pure
+ Python manipulation. In other words, don't look at this file
+ for an example of how easy it is to use SCons to build "normal"
+ software.)
src/
Where the actual source code is kept, of course.