Skip to content
Snippets Groups Projects
Commit 6aec0f2b authored by Francois-Rene Rideau's avatar Francois-Rene Rideau
Browse files

2.018.13: in 2.017.12 I made the mistake of changing the signature

of some internal functions though they may be in the continuation
of an asdf upgrade, because asdf could be loaded by a .asd file
we load while finding a system for a dependency.
Solution: unintern the symbols during an upgrade.
parent eceda9a0
No related branches found
No related tags found
No related merge requests found
......@@ -14,7 +14,7 @@
:licence "MIT"
:description "Another System Definition Facility"
:long-description "ASDF builds Common Lisp software organized into defined systems."
:version "2.018.12" ;; to be automatically updated by bin/bump-revision
:version "2.018.13" ;; to be automatically updated by bin/bump-revision
:depends-on ()
:components
((:file "asdf")
......
;;; -*- mode: Common-Lisp; Base: 10 ; Syntax: ANSI-Common-Lisp -*-
;;; This is ASDF 2.018.12: Another System Definition Facility.
;;; This is ASDF 2.018.13: Another System Definition Facility.
;;;
;;; Feedback, bug reports, and patches are all welcome:
;;; please mail to <asdf-devel@common-lisp.net>.
......@@ -107,7 +107,7 @@
;; "2.345.6" would be a development version in the official upstream
;; "2.345.0.7" would be your seventh local modification of official release 2.345
;; "2.345.6.7" would be your seventh local modification of development version 2.345.6
(asdf-version "2.018.12")
(asdf-version "2.018.13")
(existing-asdf (find-class 'component nil))
(existing-version *asdf-version*)
(already-there (equal asdf-version existing-version)))
......@@ -226,7 +226,7 @@
#:compile-file* #:source-file-type)
:unintern
(#:*asdf-revision* #:around #:asdf-method-combination
#:split #:make-collector
#:split #:make-collector #:do-dep #:do-one-dep
#:output-files-for-system-and-operation) ; obsolete ASDF-BINARY-LOCATION function
:export
(#:defsystem #:oos #:operate #:find-system #:run-shell-command
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment