Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
A
asdf
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Tarn Burton
asdf
Commits
9c352ea4
Commit
9c352ea4
authored
9 years ago
by
Francois-Rene Rideau
Browse files
Options
Downloads
Patches
Plain Diff
Tweak to TODO: simplify upgrade, etc.
parent
67fb9905
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
TODO
+16
-12
16 additions, 12 deletions
TODO
with
16 additions
and
12 deletions
TODO
+
16
−
12
View file @
9c352ea4
* Decree that versions older than 2 years are not supported;
* Decree that versions older than 2 years are not supported;
yet, keep supporting an upgrade from whatever vendors provide
yet, keep supporting an upgrade from whatever vendors provide
— so push them to provide recent stuff.
— so push them to provide recent stuff.
Already, swank-asdf doesn't support anything older than 2.014.6
** Already, swank-asdf doesn't support anything older than 2.014.6
(as provided by the first 2011 iteration of Quicklisp), and
(as provided by the first 2011 iteration of Quicklisp), and
I (fare) am pushing for swank-asdf to not support anything older
I (fare) am pushing for swank-asdf to not support anything older
than 3.0 (since no maintained implementation has anything older,
than 3.0 (since no maintained implementation has anything older,
with the LispWorks 7.0 release being last to upgrade, in May 2015).
with the LispWorks 7.0 release being last to upgrade, in May 2015).
Maybe remove old versions from upgrade tests; or maybe not:
** Maybe remove old versions from upgrade tests; or maybe not:
if we support old versions in any way,
if we support old versions in any way,
it should be for upgrade only, and "punt" is acceptable.
it should be for upgrade only, and "punt" is acceptable.
Upgrade tests might be split in two test sets: short and long.
** Maybe remove upgrade from antique ASDF altogether.
Clear all the code in the header, and/or
move a few elements to asdf/upgrade.
** Upgrade tests might be split in two test sets: short and long.
* Moving toward cross-compilation (ASDF 3.2? 4?)
* Moving toward cross-compilation (ASDF 3.2? 4?)
This would allow to get most of the benefits of XCVB
This would allow to get most of the benefits of XCVB
...
@@ -231,7 +234,8 @@
...
@@ -231,7 +234,8 @@
* Bug found by fe[nl]ix: infinite loop if the definitions in an asd file
* Bug found by fe[nl]ix: infinite loop if the definitions in an asd file
are not in strict defsystem-depends-on dependency order.
are not in strict defsystem-depends-on dependency order.
** At least document the issue.
** At least document the issue.
** Real solution: defer parsing and evaluation of defsystem forms.
** Real solution: defer parsing and evaluation of defsystem forms?
Or simply detect circularity and issue an appropriate error?
* Include some ABL test for stassats's (now obsolete?) thing:
* Include some ABL test for stassats's (now obsolete?) thing:
(asdf:enable-asdf-binary-locations-compatibility
(asdf:enable-asdf-binary-locations-compatibility
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment