1.0.9.7: the MSI should not add .lisp and .fasl associations

* It could, but not without asking permission.

diff --git a/NEWS b/NEWS
index d89493e..1393e53 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,7 @@
 ;;;; -*- coding: utf-8; -*-
 changes in sbcl-1.0.10 relative to sbcl-1.0.9:
+  * minor incompatible change: the MSI installer on Windows no longer
+    associates .lisp and .fasl files with the installed SBCL.
   * minor incompatible change: :UNIX is no longer present in *FEATURES*
     on Windows. (thanks to Luis Oliviera)
   * optimization: SLOT-VALUE and (SETF SLOT-VALUE) are now >20% faster

diff --git a/tools-for-build/wxs.lisp b/tools-for-build/wxs.lisp
index a6f1678..364ef50 100644 (file)
--- a/tools-for-build/wxs.lisp
+++ b/tools-for-build/wxs.lisp
@@ -232,8 +232,13 @@
                             "Name" "PATH"
                             "Part" "first"
                             "Value" "[INSTALLDIR]"))
-            ,(make-extension "fasl" "application/x-lisp-fasl")
-            ,(make-extension "lisp" "text/x-lisp-source")
+            ;; If we want to associate files with SBCL, this
+            ;; is how it's done -- but doing this by default
+            ;; and without asking the user for permission Is
+            ;; Bad. Before this is enabled we need to figure out
+            ;; how to make WiX ask for permission for this...
+            ;; ,(make-extension "fasl" "application/x-lisp-fasl")
+            ;; ,(make-extension "lisp" "text/x-lisp-source")
             ("File" ("Id" "sbcl.exe"
                      "Name" "sbcl.exe"
                      "Source" "../src/runtime/sbcl.exe")

diff --git a/version.lisp-expr b/version.lisp-expr
index 8b7d8c1..1a24b50 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.9.6"
+"1.0.9.7"