Commit 51e49a2a authored by Francois-Rene Rideau's avatar Francois-Rene Rideau
Browse files

Configuration, output translations

parent 96480309
......@@ -223,10 +223,44 @@ sub-bullet under a major header.
** Configuration Difficulties
*** ASDF1 locates system definition files using a =\*central-registry\*=
*** But who configures it when?
**** .sbclrc, .ccl-init => onus on the user
**** =common-lisp-controller= => onus on the distributor
**** A program building script => onus on the release manager
*** ASDF2: decentralized source registry
**** environment variable, configuration files, defaults
*** *each can specify what he knows, none need specify what he doesn't*
**** Essential principle for responsibility over configuration
*** COMMENT ASDF1: someone must manage integration of everything
** Output locations
*** CL isn't a single-implementation language.
**** Each version of each implementation has its own FASL format
*** Many ASDF1 extensions to move FASLs away (ABL, CLC, CL-launch)
**** Need to be magically loaded and configured
**** No consensual solution on where to put things
*** ASDF2: configurable output translations, sensible defaults
*** Unaddressed: further configuration discrepancies (e.g features, etc.)
**** ASDF won't ever do it. XCVB will (not yet).
** Dependency Bugs
*** Changes within a module didn't cause recompilation of dependent components
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment