- 16 Oct, 2016 1 commit
-
-
Francois-Rene Rideau authored
If we fmakunbound a defgeneric, we lose any user-defined method on the function and must therefore reload any and every system that might have defined methods on it. We must therefore not fmakunbound past the forward compatibility upgrade trigger, only before. Adjust our code accordingly. Conservative bounds are used in *oldest-forward-compatible-asdf-version* and redefined-functions that should probably be refined after some inspection of old versions. This is a response to https://bugs.launchpad.net/asdf/+bug/1631771
-
- 25 Sep, 2016 2 commits
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
Also make traverse-actions and required-components simple defuns. It's unclear why they were in action. Maybe at some point in the past, they have been used earlier in the build.
-
- 21 Sep, 2016 1 commit
-
-
Robert Goldman authored
-
- 20 Sep, 2016 1 commit
-
-
Francois-Rene Rideau authored
-
- 10 Jan, 2016 1 commit
-
-
Robert Goldman authored
-
- 08 Jan, 2016 1 commit
-
-
Francois-Rene Rideau authored
Fixes lp#1531887, whereby some actions all dependencies of which were already done would be given the wrong timestamp after perform, and every plan tried to do them anew.
-
- 24 Mar, 2014 2 commits
-
-
Francois-Rene Rideau authored
* override for prepare-op is on component-depends-on, not perform. * coerce-class must be defined after call-function, and accept *package* for now.
-
Francois-Rene Rideau authored
Also, override prepare-op on systems to use *load-system-operation*, so that all the efforts of load-bundle-op aren't negated by the first-come compilation.
-
- 14 Mar, 2014 1 commit
-
-
Francois-Rene Rideau authored
Refactor COMPONENT class designators to use the same general method. As a substrate, goodbye uiop/utility:find-class*, hello uiop/utility:coerce-class. In the operate upgrade handler, assume there is no uninterning and renaming packages away anymore going forward. Add tests for strings as class designators using defsystem-depends-on.
-
- 13 Mar, 2014 1 commit
-
-
Robert P. Goldman authored
-
- 28 Feb, 2014 1 commit
-
-
Robert P. Goldman authored
-
- 23 Feb, 2014 1 commit
-
-
Robert P. Goldman authored
-
- 18 Feb, 2014 1 commit
-
-
Francois-Rene Rideau authored
(If it's not backward, it's not compatible.)
-
- 12 Feb, 2014 1 commit
-
-
Francois-Rene Rideau authored
by only effecting them on parent classes. Also, do the sideways dependencies FIRST.
-
- 31 Jan, 2014 1 commit
-
-
Francois-Rene Rideau authored
Remove some trailing spaces.
-
- 27 Jan, 2014 4 commits
-
-
Francois-Rene Rideau authored
Paper over GCL failure in test-operation-classes; tweak test. Tweak Makefile for one more test.
-
Francois-Rene Rideau authored
* Add some comments on TRAVERSE-ACTION; expand those on SOURCE-FILE-TYPE. * Remove a few unnecessary input-files or output-files methods * Remove (declare (ignorable ...)) for specialized arguments. Specialize a few arguments to T. * Remove most when-upgrading methods, since we drop data on old incompatible ASDFs.
-
Francois-Rene Rideau authored
For backward compatibility with ASDF 2, an operation that doesn't explicitly inherit from one of the propagation classes or non-propagating-operation will be downward- and sideway- propagating, with a warning at instantiation. Inheriting from non-propagating and a propagating class at the same time yields an error, not a warning. Update packages and tests.
-
Francois-Rene Rideau authored
* load-op needn't be sideway, its sideway dependencies are already provided by prepare-op * compile-op should use compile-op (default) not load-op as its downward-operation. * no need for an input-files method for prepare-op, nil is the global default. * Some documentation for compute-action-stamp. * Don't skip upgrade from 1.x on Allegro anymore, since we now correctly punt. * Instead of asdf/package:define-package, use the canonical name uiop/package:define-package
-
- 26 Jan, 2014 1 commit
-
-
Robert P. Goldman authored
-
- 21 Jan, 2014 5 commits
-
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
-
Robert P. Goldman authored
The behavior of OPERATION has changed: previously it would act roughly like LOAD-OP, and automatically have dependencies, but now that behavior has been removed in a clean-up. In order to support programmers, we attempt to detect programmer-defined OPERATION subclasses and signal an error if we believe they are unpatched. The new dependency-handling is implemented in the classes DOWNWARD-OPERATION, UPWARD-OPERATION, SIDEWAY-OPERATION, SELFWARD-OPERATION, and the newly-added NON-PROPAGATING-OPERATION. To detect unpatched OPERATION classes, when we are instantiating an OPERATION, we check to make sure it has one of the above classes as a superclass. If it does not, we raise a continuable error. This is done in an INITIALIZE-INSTANCE :BEFORE method on OPERATION. We considered trying to detect the definition of OPERATION subclasses, but because the MOP is not standard, that approach was rejected as infeasible. Add NON-PROPAGATING-OPERATION as superclass where needed. Further checks and some documentation. Thanks to Fare for advice. Check that no OPERATION is both propagating and non-propagating. Thanks to Fare for the suggestion.
-
Robert P. Goldman authored
Added INITIALIZE-INSTANCE that checks for operations that have no specified dependency propagations. Also added NON-PROPAGATING-OPERATION as a way to specify that an OPERATION subclass /intentionally/ performs no dependency propagation.
-
- 09 Jan, 2014 1 commit
-
-
Francois-Rene Rideau authored
-
- 08 Jan, 2014 1 commit
-
-
Francois-Rene Rideau authored
Work around spurious warning on LispWorks.
-
- 07 Jan, 2014 4 commits
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
Also fix the name of the :initarg for upward-operation (oops).
-
Robert P. Goldman authored
-
- 09 Oct, 2013 1 commit
-
-
Francois-Rene Rideau authored
-
- 09 Jun, 2013 1 commit
-
-
Francois-Rene Rideau authored
-
- 08 Jun, 2013 1 commit
-
-
Francois-Rene Rideau authored
For consistency, MAKE-PLAN always returns a plan. For backward compatibility, TRAVERSE always returns a list of actions. OPERATE now calls MAKE-PLAN, not TRAVERSE anymore. Happily, no one in quicklisp defines *useful* methods on TRAVERSE. Thanks to foom for suggesting this cleanup.
-
- 17 Mar, 2013 1 commit
-
-
Francois-Rene Rideau authored
Rename sibling-operation sideway-operation, sibling-dependencies sideway-dependencies. No one in quicklisp was using the old name. Introduce selfward-operation for the common pattern. Have a prepare-fasl-op to gracefully propagate fasl-op. Reset component-depends-on when upgrading. Refactor concatenate-source-op in a likewise fashion.
-
- 03 Mar, 2013 1 commit
-
-
Francois-Rene Rideau authored
Another pass package upgrade. Export FEATURE from correct package. Use package :asdf-user when reading file for version.
-
- 22 Feb, 2013 1 commit
-
-
Francois-Rene Rideau authored
Export component-loaded-p. Update some docstrings.
-
- 06 Feb, 2013 2 commits
-
-
Francois-Rene Rideau authored
Also, decouple with-muffled-compiler-condtions from with-saved-deferred-warnings.
-
Francois-Rene Rideau authored
1- To make life easier on Xach, stop requiring asdf.lisp to be loaded as source before it's compiled. Instead, wrap each and every single form in an eval-when, most of the time via the with-upgradability macro that also transforms defun into defun* and defgeneric into defgeneric*. Causes massive reindentation :-( 2- Have a proper :version for fallback systems. Will make systems that check the version happier. 3- protect a condition with #+sb-eval. Fixes lp#1116408. 4- Protect warnings-file methods with dynamic when *warnings-file-type* rather than static #+.
-