- 04 May, 2018 1 commit
-
-
Francois-Rene Rideau authored
-
- 08 Apr, 2018 2 commits
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- 07 Mar, 2018 5 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
Set source file of package-inferred-systems to source file of primary system See merge request asdf/asdf!93
-
Robert Goldman authored
-
Robert Goldman authored
-
Robert Goldman authored
Add support for the Mezzano Common Lisp operating system See merge request asdf/asdf!94
-
- 01 Mar, 2018 3 commits
-
-
Peter Housel authored
-
Eric Timmons authored
This ensures that primary-system-name gives the name of the primary system when passed a package-inferred-system object. Add test to catch this regression in the future.
-
Peter Housel authored
These changes add support for the Mezzano operating system and its Common Lisp implementation. They are based on changes originally developed by Henry Harrington against ASDF 3.1.7.
-
- 20 Feb, 2018 3 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
-
Robert Goldman authored
Add DEPENDENCY-NOT-DONE condition. Refine the printing of such warnings. Later we may wish to export this condition, if we can identify when it should be muffled.
-
- 19 Feb, 2018 2 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
Define package fixes See merge request asdf/asdf!92
-
- 17 Feb, 2018 2 commits
-
-
Eric Timmons authored
SBCL has been getting aggresive with checking arguments to functions. For some reason (as of SBCL 1.4.1), setting the package source location in define-package seems to trigger a source translation for the apply form that ends up producing (many) compilation notes that the arguments to ensure-package in the keyword positions are not constant, weakening keyword argument checking. We can get around that, however, by using a funcall directly.
-
Eric Timmons authored
Tested on SBCL 1.4.4. If sb-c:source-location is evaluated during macro expansion, then the source location will always point to asdf.lisp (inside the define-package macro). If it is evaluated after macro expansion, it points to the right place.
-
- 16 Jan, 2018 2 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
Misnamed secondary See merge request asdf/asdf!91
-
- 03 Jan, 2018 2 commits
-
-
Francois-Rene Rideau authored
Distinguish between "syntactic" primariness ("foo" vs "foo/bar" names) and "semantic" primariness (system foo in foo.asd vs system foo in bar.asd), and use the right one at all right place: when checking if a system is up-to-date, what matters is that the old primary system is at the same place as before, and is up-to-date. Thinking about it, there is a lingering bug in case a definition-dependency are up-to-date, but were modified after the definition was read. What is really needed is a prepare-define-op. Sigh.
-
Francois-Rene Rideau authored
Test whether ASDF is still confused by misnamed secondary systems: https://bugs.launchpad.net/asdf/+bug/1739514
-
- 18 Dec, 2017 3 commits
-
-
Francois-Rene Rideau authored
-
Robert Goldman authored
-
Robert Goldman authored
Add package location information on SBCL See merge request asdf/asdf!90
-
- 17 Dec, 2017 1 commit
-
-
Francois-Rene Rideau authored
Enhance define-package so SBCL can locate the source-location of the package.
-
- 15 Dec, 2017 2 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
-
- 12 Dec, 2017 3 commits
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- 06 Dec, 2017 1 commit
-
-
Francois-Rene Rideau authored
-
- 05 Dec, 2017 3 commits
-
-
Francois-Rene Rideau authored
Change implementation strategy for operation metadata methods bundle-type, gather-operation and gather-type. Upgrading from 3.1.7 or earlier yielded incorrect values for the metadata slots of the bundle operation classes, e.g. (gather-type (make-operation 'monolithic-lib-op))) was stuck to :STATIC-LIBRARY instead of its correct value :OBJECT since 3.2.0. The reason was that we were storing the value for this method in the :initform for the slot gather-type, which started as clever way of defining it as part of the DEFCLASS form for the class itself; however, this usage pattern does not work well with hot code upgrade: if the :initform changes during ASDF upgrade, the slot is already initialized, so its value isn't updated. That would require a method on UPDATE-INSTANCE-FOR-REDEFINED-CLASS, which hopefully should be invoked despite the fact that the shape of the class hasn't changed. A new slot won't be allocated because (a) we ensure that our operation classes are sing...
-
Francois-Rene Rideau authored
Test more versions during upgrade tests.
-
Francois-Rene Rideau authored
-
- 01 Dec, 2017 2 commits
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- 14 Nov, 2017 2 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
-
- 12 Nov, 2017 1 commit
-
-
Robert Goldman authored
-