wanted: :extend-configuration for initialize-source-registry

[Attila Lendvai]

i wanted to extend the current value of the source registry and thought that :inherit-configuration does that, but to my surprise i ended up getting a source registry with stuff coming from the config files.

what i'm looking for is a way to add stuff to the current state of the registry. i'm not sure the :extend-configuration name communicates the intention well enough though...

[Faré (fahree)]

Several people have asked for a way to extend the current configuration. I suppose that's a real need, then.

What about:

1- saving whatever parameter initialize-source-registry was called with.

2- then you can use this and extend it.

3- but it will recurse into the configuration files and pick up new content from them, if you :inherit-configuration.

[Faré (fahree)]

In 2.012.8, I had asdf remember the parameter passed to initialize-source-registry. You could use that at the thing you extend. Hum. I failed to export the symbol asdf::*source-registry-parameter* though -- tell me if it suits you.

[Attila Lendvai (attila-lendvai)]

fyi, since then i've reworked our stuff a bit and i've straight out added a (asdf:clear-source-registry) to our initialization file, so that the environment is completely deterministic regardless of the state in /etc/ and stuff like that.

in short:
 - clear the registry
 - assume the path of hu.dwim.asdf project is relative to the init.lisp file, put it in the registry and load it
 - the code in hu.dwim.asdf scans some directories and calls initialize-source-registry with them with :ignore-inherited-configuration
 - it also struggles a bit with slime's hostility to asdf, so that :depends-on :swank and (asdf:load-op :swank) works as expected, even if it was loaded with its own loader (as opposed to asdf).

[Faré (fahree)]

OK. If you have a satisfactory solution, I'm marking as Won't Fix.