1. 26 Oct, 2017 1 commit
  2. 22 Oct, 2017 1 commit
  3. 21 Oct, 2017 1 commit
  4. 20 Oct, 2017 3 commits
    • Francois-Rene Rideau's avatar
      Extend the set of versions from which to test upgrade · bfbefcec
      Francois-Rene Rideau authored
      A recent manual test found a bug upgrading from 3.2.1.
      So include that in the test set.
      New policy: include first and last of the last few ASDF series, not just last.
    • Francois-Rene Rideau's avatar
      Rename stamp to timestamp in uiop/utility · c6654583
      Francois-Rene Rideau authored
      Restore backward compatibility with older versions of ASDF (before 3.3.0)
      by renaming stamp< and its friends to timestamp<, etc.
      Sometime in the lead-up to ASDF 3.3.0, I changed the encoding of infinities
      from NIL is -infinity and T is +infinity to T is -infinity and T is +infinity
      which made the code notably nicer on the ASDF side, because file-write-date
      would return directly the correct result instead of having to constantly switch
      between inverse conventions. However --- big mistake --- I kept the same
      function name, after checking that the functions had no user in Quicklisp,
      no one who had ever discussed them but me, and no documentation before 3.2.0
      except a single comment line for the entire family of functions.
      This doesn't matter as long as ASDF and UIOP are kept in synch, but such is
      not the case with Quicklisp, where Xach both welcomes recent UIOP releases
      but refuses to include updates to ASDF itself. Then, loading a new UIOP
      with reverse conventions totally confuses the old ASDF, and causes spurious
      rebuilds of everything after UIOP is loaded -- multiple times if present
      in multiple phases (that and slower build times is how Xach noticed the bug).
      The solution adopted is to give a new name to the functions with a different
      convention -- timestamp< instead of stamp<, and so on. Therefore,
      the new ASDF 3.3.1 will expect the new convention from UIOP 3.3.1,
      that will no longer overwrite the functions from ASDF 3.2.1 and older with
      backward-incompatible variants. If an old ASDF 3.2.1 or earlier loads
      a newer UIOP 3.3.1 or later, it will keep using the old functions:
      the symbols for these functions will be uninterned, but
      the values for these functions which won't be clobbered anymore.
      Backward compatibility is a strong requirement not to to break lightly,
      not even in a subtle way, not even if "nobody else is using it" ---
      an older version of ASDF is already "somebody else" with respect to UIOP.
    • Francois-Rene Rideau's avatar
      Add upgrade test for UIOP issue that Xach found. · 40020f7d
      Francois-Rene Rideau authored
      UIOP 3.3.0 loaded on top of an earlier ASDF 3 would cause everything to be
      spuriously rebuilt, because of a change of representation of stamp< arguments.
      This test evidences the breakage, and the fix.
  5. 12 Oct, 2017 5 commits
  6. 08 Oct, 2017 1 commit
  7. 06 Oct, 2017 6 commits
  8. 19 Sep, 2017 1 commit
  9. 14 Sep, 2017 1 commit
  10. 11 Sep, 2017 2 commits
  11. 06 Sep, 2017 5 commits
  12. 02 Sep, 2017 2 commits
  13. 01 Sep, 2017 5 commits
  14. 30 Aug, 2017 1 commit
  15. 22 Aug, 2017 1 commit
  16. 21 Aug, 2017 1 commit
  17. 01 Aug, 2017 1 commit
  18. 30 Jul, 2017 1 commit
  19. 26 Jul, 2017 1 commit
    • Francois-Rene Rideau's avatar
      Fix more upgrade issues · 65d16a93
      Francois-Rene Rideau authored
      Use :recycle of :asdf/find-system in :asdf/source-registry to migrate symbol
      initialize-source-registry that moved from that previous packages
      (otherwise, upgrade from 3.2.1 breaks on all lisps).
      Also :recycle :asdf/action in :asdf/plan for required-components and
      traverse-action. But avoid interning plan in asdf/action so it doesn't
      confuse clisp when upgrading from 2.26(!).