Hi Zack,
[ Not sure if quicklisp-controller is the appropriate place for this. Apologies if not. ]
Currently, Quicklisp uses "cl-clon" to name Clon. Could you please change that to "net.didierverna.clon" instead ? The reason I'm asking is to have Quicklisp's name equal to Clon's primary system name.
Quickref uses a heuristic to determine a Quicklisp release's primary system (when several systems are provided), and that heuristic attempts to match a system name against the release name. Because nothing in Clon is named "cl-clon", Quickref ends up documenting one of the demo programs instead (it's called "simple").
AFAICR, "cl-clon" was originally used because "clon" was already taken by another library (which seems gone now).
To be fair, my two Clon demo systems are just named "simple.asd" and "advanced.asd", and this is very bad. I will fix them with a fully qualified prefix in the next release.
Thank you!
Hi Zack,
[ Not sure if quicklisp-controller is the appropriate place for this. Apologies if not. ]
Currently, Quicklisp uses "cl-clon" to name Clon. Could you please change that to "net.didierverna.clon" instead ? The reason I'm asking is to have Quicklisp's name equal to Clon's primary system name.
Quickref uses a heuristic to determine a Quicklisp release's primary system (when several systems are provided), and that heuristic attempts to match a system name against the release name. Because nothing in Clon is named "cl-clon", Quickref ends up documenting one of the demo programs instead (it's called "simple").
AFAICR, "cl-clon" was originally used because "clon" was already taken by another library (which seems gone now).
To be fair, my two Clon demo systems are just named "simple.asd" and "advanced.asd", and this is very bad. I will fix them with a fully qualified prefix in the next release.
Thank you!