Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
A
asdf
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
1
Issues
1
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Hugo Ishimaru
asdf
Commits
a720e02f
Commit
a720e02f
authored
Dec 19, 2013
by
Francois-Rene Rideau
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update TODO
parent
db6a7b33
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
7 deletions
+8
-7
TODO
TODO
+8
-7
No files found.
TODO
View file @
a720e02f
* Decree that versions older than 2 years are not supported,
remove them from upgrade tests. We should already not support
anything older than 2.014.5 from Quicklisp, or so.
Yet, we should keep supporting upgrading from what vendors provide.
* Improve upgrade so that we don't lose state when upgrading from a "recent enough" ASDF.
This requires better upgrade tests, with hot data.
Yet, we should keep supporting upgrading from what vendors provide
— so push them to provide recent stuff.
* ASDF 3.2: moving toward cross-compilation.
This would allow to get all or most of the benefits of XCVB
...
...
@@ -13,10 +11,13 @@
** Need to further split asdf:perform in two parts:
A part that runs on the host and specifies (as SEXP or string to read)
a form that must be evaluated on the target machine, not the host.
A trivial that runs on the target
and doesn't require ASDF or CLOS installed there (though maybe UIOP).
** Audit all the current users of perform, and offer them a new way;
A trivial that runs on the target and doesn't require the network
of objects related to the ASDF plan to be present,
or even ASDF itself, for the matter (though UIOP, yes, for sanity).
** Audit all the current specializers of perform, and offer them a new way;
they can keep the perform method to run on older versions of ASDF.
** Modify SBCL and other implementations so they provide UIOP
independently from ASDF?
* Some out-of-line configuration mechanism for various options?
i.e. have files that override some variables around compilation of some systems.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment