On 01 Aug 2015, at 12:00, Ralph Ritoch <rritoch@gmail.com> wrote:
Mark,
I have one additional issue to add to the configuration discovery process. The original concept of using a /META-INF/abcl-contrib/version.lisp file accounts for web based classpaths while the *-conf.d pattern does not due to the fact that it is often not possible to get a list of files for web based classpaths. To accommodate this a default configuration file list would also be needed, such as /META-INF/abcl-config-sources.lisp . I am aware that this creates a huge potential for conflict as various libraries could each contain this file, but the web deployment process would need to ensure that all of the configuration files in the *-conf.d are included in this file when the classpath will be accessed remotely but not from within a jar.
Then I would suggest that we further ape the ASDF source registry mechanism by checking for the existence of a jar:file:SOME.jar!/META-INF/common-lisp/source-registy.conf file as well.