[git] CMU Common Lisp branch master updated. snapshot-2014-06-33-ge9be6b4

[Raymond Toy]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMU Common Lisp".

The branch, master has been updated
       via  e9be6b48a40993444db72d4a9434b9eb44099f65 (commit)
       via  040e27416d95cf0980d2e77f70f9430c1ff4e769 (commit)
      from  3b8bd8385a96685faeb26da60d9394feafb79907 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit e9be6b48a40993444db72d4a9434b9eb44099f65
Author: Raymond Toy <toy.raymond at gmail.com>
Date:   Thu Jul 31 17:05:47 2014 -0700

    Add info for cross-compile scripts.

diff --git a/src/bootfiles/README b/src/bootfiles/README
index c96ff68..31890a7 100644
--- a/src/bootfiles/README
+++ b/src/bootfiles/README
@@ -12,3 +12,23 @@ fix that here is the convention to be used for all bootfiles after
    sequentially from 1 (n).  Thus, the boot-2014-06-1.lisp is intended
    to be built from the 2014-06 snapshot, and is the first boot file
    to be applied.
+3. The boot file should describe what it is for.
+
+If a cross-compile script is needed, we also have similar rules.
+
+1. The script must be in the version directory, as for boot files.
+2. The names of the script file must have to format
+   boot-yyyy-mm-n-cross-aaa.lisp where yyyy, mm, and n have the same
+   meaning as for boot files above.  
+
+   A. The aaa field is flexible. 
+      1. If it is not included, then the script is intended to be
+         applicable to all architectures.  If aaa is given, then it is
+         meant to be applied only for the architecture aaa.
+      2. If the scrit is applicable to more than one architecture, the
+         aaa field is dropped and the script must take care to include
+         conditionals so that the script can be applied to all
+         architectures.
+   B. Additional information can be included if desired.
+
+3. The script should describe what it is for.

commit 040e27416d95cf0980d2e77f70f9430c1ff4e769
Author: Raymond Toy <toy.raymond at gmail.com>
Date:   Thu Jul 31 16:57:41 2014 -0700

    Add README to document the naming convention of boot files.

diff --git a/src/bootfiles/README b/src/bootfiles/README
new file mode 100644
index 0000000..c96ff68
--- /dev/null
+++ b/src/bootfiles/README
@@ -0,0 +1,14 @@
+The nameing of the bootfiles have been historically inconsistent. To
+fix that here is the convention to be used for all bootfiles after
+2014-07.
+
+1. The bootfile must reside in the directory whose name is the current
+   CMUCL version for which this bootfile applies.  For example, as of
+   this writing, the current version is 20e, so boot files must be in
+   the 20e directory.
+2. The name of the boot file shall be boot-yyyy-mm-n.lisp where
+   yyyy-mm represents the year (yyyy) and month (mm) of the snapshot
+   that is used to build from.  The boot files are numbered
+   sequentially from 1 (n).  Thus, the boot-2014-06-1.lisp is intended
+   to be built from the 2014-06 snapshot, and is the first boot file
+   to be applied.

-----------------------------------------------------------------------

Summary of changes:
 src/bootfiles/README |   34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100644 src/bootfiles/README


hooks/post-receive
-- 
CMU Common Lisp