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
Container Registry
Model registry
Operate
Environments
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
Hugo Ishimaru
asdf
Commits
af0cb12e
Commit
af0cb12e
authored
10 years ago
by
Francois-Rene Rideau
Browse files
Options
Downloads
Patches
Plain Diff
Update TODO.
parent
55ef228a
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
+17
-2
17 additions, 2 deletions
TODO
with
17 additions
and
2 deletions
TODO
+
17
−
2
View file @
af0cb12e
...
@@ -5,7 +5,7 @@
...
@@ -5,7 +5,7 @@
(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 2.019 (still used by LispWorks 6.1).
than 2.019 (still used by LispWorks 6.1).
Hopefully, sometime in 2014, everyone will have adopted ASDF 3.
Hopefully, sometime in 2014, everyone will have adopted ASDF 3
, or even 3.1.1
.
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.
...
@@ -230,7 +230,7 @@
...
@@ -230,7 +230,7 @@
is anyone still using the compatibility mode?
is anyone still using the compatibility mode?
Maybe issue a warning, then a cerror, before to remove the code?
Maybe issue a warning, then a cerror, before to remove the code?
* Make load-op a generic operation that selects the proper strategy
* Make load-op a generic operation that selects the proper strategy
?
for each system, module or file, according to component properties and user-configuration:
for each system, module or file, according to component properties and user-configuration:
compile the lisp file then load the fasl (load-fasl-op on a cl-source-file),
compile the lisp file then load the fasl (load-fasl-op on a cl-source-file),
load the lisp file without compiling (load-source-op),
load the lisp file without compiling (load-source-op),
...
@@ -378,3 +378,18 @@ It looks like SWANK can be fixed soon, though, so we'll see.
...
@@ -378,3 +378,18 @@ It looks like SWANK can be fixed soon, though, so we'll see.
after the package created if it doesn't exist yet (!)
after the package created if it doesn't exist yet (!)
*** There again, a check that a forward-package is not backward
*** There again, a check that a forward-package is not backward
would be very nice.
would be very nice.
* Migrate from component-depends-on to action-depends-on
** I contend a future version of ASDF will replace
(component-depends-on operation component)
with (action-depends-on plan operation component).
This allows for different normalization strategies for dependencies
(including strategies that avoid resolving things to NIL),
a reified context for featurep checks, etc.
** Easy but long backward-compatible transition:
*** get all users to use the new gf and keep extending both new and old gf,
meanwhile the new gf has an around method that actually calls the old gf
except in testing mode and/or if we can check that they're using the new convention
*** when everyone has migrated, remove the old mode and the short-circuit.
** However, we cannot deprecate component-depends-on yet — not until we have
some transition in place to a better interface.
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