© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The strong case for making it part of asdf.lisp is that if it is a contrib nobody will use because it will not be available by default. Contribs in other packages are either done so because of stupid political questions (see slime's fancy mode) or because they may hinder functionality, are not portable or have a humongous cost (cffi-grovel)
The point of all this is motivating people to move towards good practices, avoiding use of ASDF's API, system interrogation and all other dependencies that may or may not be available at run time. The point of all this is making system building more and more independent of the libraries and pathname translations going all behind...
I wrote already several thousand words about the utility and interest of this for ASDF's future.
Why do you not answer instead the following question:
Is there a strong case for making this a contrib and not part of asdf.lisp?