X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=doc%2FPACKAGING-SBCL.txt;h=31155495052768ae375e579233f909124ef5c703;hb=d6f9676ae94419cb5544c45821a8d31adbc1fbe8;hp=33abe8341ff66eda196bca3227f7836fa128eb8e;hpb=09526ad4e54d7858d678aa2ac372261331a185a5;p=sbcl.git

diff --git a/doc/PACKAGING-SBCL.txt b/doc/PACKAGING-SBCL.txt
index 33abe83..3115549 100644
--- a/doc/PACKAGING-SBCL.txt
+++ b/doc/PACKAGING-SBCL.txt
@@ -1,19 +1,24 @@
 Packaging SBCL
 ==============
 
-If you package SBCL for a distribution, please edit version.lisp-expr,
-and append ".packaging-target-or-patch[.version]".
+If you package SBCL for distribution, we ask that you to take steps to
+make the version number reflect this. Our users often report bugs that
+are intimately tied up with configuration issues, and much confusion
+can result from mistaking a packaged SBCL for the upstream one.
+
+If you are working from a Git branch, all you need to do is make sure
+the branch name reflects the situation -- the build system will
+incorporate the it in the version string.
+
+If you are working from a release tarball, please edit
+version.lisp-expr, and append ".packaging-target-or-patch[.version]".
 
 Examples:
 
- "1.0.7.gentoo"
- "1.0.7.mikes-rpms.2"
+ "1.0.50.gentoo"
+ "1.0.50.mikes-rpms.2"
 
 This will make the startup banner, --version, and
 (lisp-implementation-version) all identify the packaged version
 correctly.
 
-We ask you to do this because users report bugs that are intimately
-tied up with configuration issues at regular intervals, and much
-confusion can result from mistaking a packaged SBCL for the upstream
-one.