1. 04 May, 2018 1 commit
  2. 08 Apr, 2018 2 commits
  3. 07 Mar, 2018 5 commits
  4. 01 Mar, 2018 3 commits
  5. 20 Feb, 2018 3 commits
  6. 19 Feb, 2018 2 commits
  7. 17 Feb, 2018 2 commits
    • Eric Timmons's avatar
      Change apply to funcall in expansion of define-package · 21e3a85b
      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.
      21e3a85b
    • Eric Timmons's avatar
      Evaluate sb-c:source-location after macroexpansion · ed0f4d5e
      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.
      ed0f4d5e
  8. 16 Jan, 2018 2 commits
  9. 03 Jan, 2018 2 commits
    • Francois-Rene Rideau's avatar
      Better handle misnamed secondary systems · 069cd2a6
      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.
      069cd2a6
    • Francois-Rene Rideau's avatar
      Massage test-multiple to check non-reloading · 5397c994
      Francois-Rene Rideau authored
      Test whether ASDF is still confused by misnamed secondary systems:
      https://bugs.launchpad.net/asdf/+bug/1739514
      5397c994
  10. 18 Dec, 2017 3 commits
  11. 17 Dec, 2017 1 commit
  12. 15 Dec, 2017 2 commits
  13. 12 Dec, 2017 3 commits
  14. 06 Dec, 2017 1 commit
  15. 05 Dec, 2017 3 commits
    • Francois-Rene Rideau's avatar
      Fix upgrade issue with asdf/bundle. · 8e68ac22
      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...
      8e68ac22
    • Francois-Rene Rideau's avatar
      Add a regression tests for upgrade · c54265da
      Francois-Rene Rideau authored
      Test more versions during upgrade tests.
      c54265da
    • Francois-Rene Rideau's avatar
      Improve test-bundle · 652d1c08
      Francois-Rene Rideau authored
      652d1c08
  16. 01 Dec, 2017 2 commits
  17. 14 Nov, 2017 2 commits
  18. 12 Nov, 2017 1 commit