asdf merge requestshttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests2024-02-20T03:04:45Zhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/233Start a history document2024-02-20T03:04:45ZFrançois-René RideauStart a history documentMove some documentation from the homepage to a history document.Move some documentation from the homepage to a history document.3.4.0François-René RideauFrançois-René Rideauhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/215Catch non-existent packages in :LOCAL-NICKNAMES clause2022-10-20T14:34:31ZMaciej Katafiasz (mathrick)Catch non-existent packages in :LOCAL-NICKNAMES clauseFixes #127Fixes #1273.4.0https://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/1873.4: :import-from-reexport clause for uiop:define-package, as per #812022-01-05T18:10:09ZPhoebe Goldman3.4: :import-from-reexport clause for uiop:define-package, as per #81As per issue #81, I implemented a `uiop:define-package` clause which imports specified symbols from a specified package, and reexports those symbols but no others. For lack of a better name, the clause is called `:import-from-reexport`. ...As per issue #81, I implemented a `uiop:define-package` clause which imports specified symbols from a specified package, and reexports those symbols but no others. For lack of a better name, the clause is called `:import-from-reexport`. I'd still welcome other suggestions. Can we just use `:reexport-from`?
My guess/hope is that this will find its home in the 3.4 release.3.4.0https://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/181Draft: `asdf:define-file-package` macro for `package-inferred-system`2022-01-07T22:41:08ZPhoebe GoldmanDraft: `asdf:define-file-package` macro for `package-inferred-system`As discussed in issue #68
I've rewritten the manual somewhat, but I don't have much experience with texinfo, so I'd appreciate reviews on that front.As discussed in issue #68
I've rewritten the manual somewhat, but I don't have much experience with texinfo, so I'd appreciate reviews on that front.3.4.0Phoebe GoldmanPhoebe Goldmanhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/169Draft: More expressive version strings and constraints2022-08-02T19:32:13ZEric TimmonsDraft: More expressive version strings and constraintsThe goal of this MR is to make specifying both version strings and version constraints more expressive.
We would like version strings to carry additional information, such as pre-release status.
We would like to expand version constrai...The goal of this MR is to make specifying both version strings and version constraints more expressive.
We would like version strings to carry additional information, such as pre-release status.
We would like to expand version constraints so that system consumers can knock out known bad versions. Additionally, system developers should be able to communicate known incompatibilities to their users.
TODO:
- [x] Get confirmation that we want our default version strings to follow [Semver](https://semver.org/spec/v2.0.0.html) grammar and ordering semantics. If not, decide on and implement another.
- [ ] Get consensus that the version-related generic functions are extensible enough to allow someone to substitute their own version string grammar and semantics.
- [x] Implement version constraints (first take at documentation is complete).
- [x] Update ASDF's build scripts to support adding pre-release information to version strings.
- [x] Update ASDF self upgrade functions to account for new version string format.
- [x] Run ASDF upgrade tests to make sure older versions of ASDF believe that newer versions are actually newer.
Closes #503.4.0Eric TimmonsEric Timmonshttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/156WIP: Record and expose provenance info for source registry2022-01-18T04:43:35ZEric TimmonsWIP: Record and expose provenance info for source registryThere was some discussion on asdf-devel on how the source registry is nearly
impossible to debug as it looks in a lot of places for configuration
information. This is an attempt to rectify that.
Goals:
+ [x] Record the reason a directo...There was some discussion on asdf-devel on how the source registry is nearly
impossible to debug as it looks in a lot of places for configuration
information. This is an attempt to rectify that.
Goals:
+ [x] Record the reason a directory is being searched for .asd files.
+ [ ] For every .asd file found in the source registry, record provenance
information as to what part of the source registry config caused that
file to be found.
+ [ ] For every .asd file found in the source registry, record if the file was
found by traversing the directory tree or if it was found in a
`.cl-source-registry.cache` file.
+ [ ] Look for .asd caches in `cl-source-registry.cache`, falling back to the
hidden version if it does not exist.
+ [ ] Add a user exposed function to print the source registry in a moderately
nice way.3.4.0https://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/133WIP: Debug helpers2022-01-05T18:10:39ZRobert GoldmanWIP: Debug helpersSome minor local refactoring to make some aspects of ASDF initialization easier to debug.
So far
* New error message.
* New local function to enable tracing.
/cc @frideauSome minor local refactoring to make some aspects of ASDF initialization easier to debug.
So far
* New error message.
* New local function to enable tracing.
/cc @frideau3.4.0Robert GoldmanRobert Goldmanhttps://gitlab.common-lisp.net/asdf/asdf/-/merge_requests/86Minimal syntax control2022-01-05T18:12:02ZFrançois-René RideauMinimal syntax controlMinimally control the `*readtable*` and other syntax variables used while building.Minimally control the `*readtable*` and other syntax variables used while building.3.4.0Robert GoldmanRobert Goldman