[Openmcl-devel] additional 1.11.x release?

Robert Goldman rpgoldman at sift.info
Tue Oct 31 07:54:49 PDT 2017


On 30 Oct 2017, at 22:48, R. Matthew Emerson wrote:

> I wonder if this would have bad effects on ASDF's fasl caching scheme.

If you want to figure out how this would affect ASDF's fasl caching, you 
can look at the value of `OUTPUT-TRANSLATIONS` after you have changed 
the version name to something you like:
```
? (asdf/output-translations::output-translations)
((#P"/Users/rpg/.cache/common-lisp/ccl-1.11-f96-macosx-x86/**/*.*" T) (T 
#P"/Users/rpg/.cache/common-lisp/ccl-1.11-f96-macosx-x86/**/*.*"))
```
in turn this relies upon `UIOP:implementation-identifier`, which uses 
`implementation-type` and `lisp-implementation-type` and 
`lisp-version-string`.  Probably seeing what happens to 
`lisp-version-string` when you change your version name is what will be 
most helpful.

Best,
r
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20171031/e8a87bca/attachment.htm>


More information about the Openmcl-devel mailing list