1. 04 Oct, 2016 1 commit
  2. 20 Sep, 2016 1 commit
  3. 13 Sep, 2016 1 commit
    • Francois-Rene Rideau's avatar
      Refactoring: introduce the function REGISTERED-SYSTEM · 7b7b9f0c
      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.
      7b7b9f0c
  4. 05 Dec, 2015 1 commit
  5. 30 Aug, 2015 1 commit
  6. 11 May, 2014 1 commit
  7. 20 Apr, 2014 2 commits
  8. 07 Jan, 2014 1 commit
  9. 04 Jan, 2014 1 commit
  10. 03 Jan, 2014 1 commit
    • Francois-Rene Rideau's avatar
      Gracefully handle the case where a package-system is missing a package. · 9ad85d7d
      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.
      9ad85d7d
  11. 23 Oct, 2013 1 commit
    • Francois-Rene Rideau's avatar
      package-system: support for quick-build style defpackage-based dependencies. · c609093c
      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*
      c609093c