asdf merge requestshttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests2016-09-09T23:17:47Zhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/8Make output determinate2016-09-09T23:17:47ZElias PippingMake output determinateThis is a proposed fix to the issues Jason Miller reported in #lisp and on the mailing list.This is a proposed fix to the issues Jason Miller reported in #lisp and on the mailing list.https://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/7Re-enable tests on macOS2016-09-09T23:50:28ZElias PippingRe-enable tests on macOSAs far as I can tell, these tests were never disabled because anything was known to be broken but rather because nobody had access to a macOS machine to test this with.As far as I can tell, these tests were never disabled because anything was known to be broken but rather because nobody had access to a macOS machine to test this with.https://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/6Use lispworks7+ feature2016-10-05T23:37:20ZElias PippingUse lispworks7+ featurehttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/4Clasp fixes2016-10-05T23:37:20ZElias PippingClasp fixesIn particular, this allows tests to be run, even though many still fail.In particular, this allows tests to be run, even though many still fail.https://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/2Small changes to ease Debian package building2016-10-05T23:37:20ZKambiz DarabiSmall changes to ease Debian package buildingThe current Makefile removes the debian/patches subdirectory, which is also ignored in .gitignore.
With this in place, it is almost impossible to patch the release sources to satisfy the Debian packaging tools (e.g. lintian).
I wou...The current Makefile removes the debian/patches subdirectory, which is also ignored in .gitignore.
With this in place, it is almost impossible to patch the release sources to satisfy the Debian packaging tools (e.g. lintian).
I would appreciate your merging these changes, so the next release could be packaged for Debian more easily.
Thanks
https://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/9Skip test-program on OpenBSD >=6.0 without wxallowed2016-10-05T23:37:20ZElias PippingSkip test-program on OpenBSD >=6.0 without wxallowedThis addresses https://bugs.launchpad.net/asdf/+bug/1621919This addresses https://bugs.launchpad.net/asdf/+bug/1621919https://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/5Detect Unicode support on Clozure CL2016-10-05T23:37:20ZElias PippingDetect Unicode support on Clozure CLhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/91Misnamed secondary2018-01-16T22:18:55ZFrançois-René RideauMisnamed secondaryFix for https://bugs.launchpad.net/asdf/+bug/1739514Fix for https://bugs.launchpad.net/asdf/+bug/17395143.3.2Robert GoldmanRobert Goldmanhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/90Add package location information on SBCL2017-12-18T00:39:04ZFrançois-René RideauAdd package location information on SBCLEnhance define-package so SBCL can locate the source-location of the package.
(Requested by Didier Verna to support Declt.)Enhance define-package so SBCL can locate the source-location of the package.
(Requested by Didier Verna to support Declt.)3.3.2Robert GoldmanRobert Goldmanhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/89Fix bundle operation upgrade issues2017-12-06T08:11:33ZFrançois-René RideauFix bundle operation upgrade issues3.3.2Robert GoldmanRobert Goldmanhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/88Extend the set of versions from which to test upgrade2017-10-22T22:40:10ZFrançois-René RideauExtend the set of versions from which to test upgradeA 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.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.3.3.1Robert GoldmanRobert Goldmanhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/87Rename stamp to timestamp in uiop/utility2017-11-12T21:05:31ZFrançois-René RideauRename stamp to timestamp in uiop/utilityRestore 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 +...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.3.3.1Robert GoldmanRobert Goldmanhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/85Preserve syntax tables in perform define-op2017-10-12T18:08:44ZFrançois-René RideauPreserve syntax tables in perform define-opASDF 3.3.0 introduced an unwanted discrepancy from 3.2.1, whereby
the readtable and print-pprint-dispatch table were not preserved
while loading a .asd file, which caused bad libraries like puri
to try to corrupt the standard readtable w...ASDF 3.3.0 introduced an unwanted discrepancy from 3.2.1, whereby
the readtable and print-pprint-dispatch table were not preserved
while loading a .asd file, which caused bad libraries like puri
to try to corrupt the standard readtable when loaded as
defsystem-depends-on dependency or equivalent.
See bug report on the asdf-devel mailing-list.
The real solution is to redo the syntax-control branch.Robert GoldmanRobert Goldmanhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/80Improve %process-status2017-09-14T11:38:59ZElias PippingImprove %process-statushttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/79Fix process-alive-p on upcoming ECL release2017-09-11T11:50:46ZElias PippingFix process-alive-p on upcoming ECL releaseSee also https://gitlab.com/embeddable-common-lisp/ecl/issues/273See also https://gitlab.com/embeddable-common-lisp/ecl/issues/273Robert GoldmanRobert Goldmanhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/78LispWorks: Document logic behind the process field2017-09-02T08:46:18ZElias PippingLispWorks: Document logic behind the process fieldhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/77Fix a warning for LispWorks on windows2017-09-01T17:47:25ZElias PippingFix a warning for LispWorks on windowsThis warning causes the test suite not to compile -- an issue
that was reported by Chun Tian (user binghe on github).This warning causes the test suite not to compile -- an issue
that was reported by Chun Tian (user binghe on github).Robert GoldmanRobert Goldmanhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/76ecl: create-image: don't call internal function compute-init-name2021-02-21T21:18:00ZDaniel Kochmańskiecl: create-image: don't call internal function compute-init-nameIt is wrong to call this function. If :init-name is not supplied, or
NIL ECL will compute the init name itself (it is not a new
mechanism).
Enabling specifying init-name makes it possible to build static and
shared libraries with known ...It is wrong to call this function. If :init-name is not supplied, or
NIL ECL will compute the init name itself (it is not a new
mechanism).
Enabling specifying init-name makes it possible to build static and
shared libraries with known initialization function (important, when
CL module is linked with bigger C/C++ project outside ASDF).
If :init-name is NIL, it will default to compute-init-name
internally. Calling explicitly is not guaranteed to work in the
future (internal mechanism).https://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/75Best practices: add table of contents2017-10-27T15:10:29ZRommel MARTINEZBest practices: add table of contentshttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/74Fix typo in UIOP README2017-07-06T23:18:03ZRommel MARTINEZFix typo in UIOP README