- 01 Mar, 2018 1 commit
-
-
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.
-
- 20 Jul, 2017 2 commits
-
-
Francois-Rene Rideau authored
Split asdf/system-registry away from asdf/find-system: the former defines the internal *defined-systems* table and the search mechanism, whereas the latter keeps the find-system methods, but also defines a new define-op operation, on load-asd will call operate. Reorder dependencies accordingly. Have forcing come from the plan, so as to not force again actions from dependencies that were already performed in a subcall to operate. Accept asdf.asd from the same version, so asdf.asd doesn't get removed at the very next call to operate (which may now come implicitly at the least provocation).
-
Francois-Rene Rideau authored
Significantly refactor plan internals. Move visited-actions, visiting-action-set, visiting-action-list, total-action-count, planned-action-count, planned-output-action-count from plan to session (remove the plan- prefix to accessors). Move sysdef-error from component to session. Remove plan as a parameter of action-valid-p (made simple defun) and while-visiting-action (both moved to action), but also map-direct-dependencies, reduce-direct-dependencies, direct-dependencies. Rename *default-plan-class* to *plan-class*, plan-record-dependency to record-dependency, plan-action-status to action-status plan-forced (accessor) to forced, plan-forced-not (accessor) to forced-not. Introduce define-op, and visit a suitable action while loading an asd file. Accumulate inner operate dependencies in a slot definition-dependencies of a registered system or a newly registered undefined-system. Introduce reset-session or reset-session-visited in various tests, so operations aren't considered as layered atop each other, but as restarting from a fresh planning session. Use with-asdf-session in required-components, make-plan. Stop using node-for, use cons directly, now that operations are safe. Export format-action from action. Move some conditions and generic functions around and reorder dependencies.
-
- 04 Oct, 2016 1 commit
-
-
- 20 Sep, 2016 1 commit
-
-
Francois-Rene Rideau authored
-
- 13 Sep, 2016 1 commit
-
-
Francois-Rene Rideau authored
Introduce the function REGISTERED-SYSTEM to abstract over finding a registered system by name, without having to take the CDR of the pair with timestamp. Also, add or improve docstrings for several functions. This refactoring should not modify any semantics, except for introducing this new function.
-
- 05 Dec, 2015 1 commit
-
-
Eric Timmons authored
Package inferred systems now inherit around-compile from their top-level system. Added test in package-inferred-system-test suite.
-
- 30 Aug, 2015 1 commit
-
-
Francois-Rene Rideau authored
rather than system-source-directory. Fixes lp#1485276
-
- 11 May, 2014 1 commit
-
-
Francois-Rene Rideau authored
-
- 20 Apr, 2014 2 commits
-
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
- 07 Jan, 2014 1 commit
-
-
Francois-Rene Rideau authored
Also fix the name of the :initarg for upward-operation (oops).
-
- 04 Jan, 2014 1 commit
-
-
Robert P. Goldman authored
-
- 03 Jan, 2014 1 commit
-
-
Francois-Rene Rideau authored
This bug was found while testing with ECL, which somehow evaluated the .asd twice during test-bundle.script when other implementations evaluated it only once; which revealed that the second time around, the package-system would override the explicit secondary definitions of test-asdf/dll-test and test-asdf/dll-user, and then would fail ungracefully due to the absence of defpackage in these files. That latent bug was present in all implementations, but not stressed by the test system.
-
- 23 Oct, 2013 1 commit
-
-
Francois-Rene Rideau authored
This is quick-build compatible and fixes lp#1230368. To use package-system, just have foo.asd containing (defsystem foo :class package-system) at the top of your quick-build hierarchy $FOODIR for packages whose name start with "FOO/" and ASDF will thereafter look for system "foo/bar/baz" in $FOODIR/bar/baz.lisp. Such a file will implicitly have its own system defined; its dependencies are computed by scanning the file, extracting its first defpackage form, and using the packages it uses or imports from as a as a specification of what systems it depends on. You can register packages as belonging to a system with (asdf:register-system-packages my-system '(package1 package2)) Using or importing from a package registered to a given system will generate a dependency to the registered system. Using or importing from a packages registered to the constant symbol T will not generate any dependency. Using or importing from a packages that is not registered will generate a dependency on a system the name of which is the package name downcased. All packages that exist at the time ASDF is initially loaded are registered to constant symbol T. Also, for convenience, introduce :use-reexport and :mix-reexport in uiop/package.lisp (of course, no one can rely on it until it's mainstream, but better late than never). To use this style in a way compatible with older versions of ASDF 3, you may use the asdf-package-system extension. See lisp-interface-library for a system that uses this style this way. Push :asdf-package-system to *features*
-