[asdf-devel] output-translations documentation

[Robert Goldman]

On 3/12/10 Mar 12 -9:46 AM, Faré wrote:
> On 12 March 2010 08:46, Robert Goldman <rpgoldman at sift.info> wrote:
>> On 3/11/10 Mar 11 -11:55 PM, Faré wrote:
>>> On 12 March 2010 00:05, Robert Goldman <rpgoldman at sift.info> wrote:
>>
>>> What other former ABL behaviour do you want me to give examples for?
>>
>> A behavior that, like ABL, creates a subdirectory for each different
>> lisp implementation.
>>
>> Would that be
>>
>> (asdf:initialize-output-translations
>>  '(:asdf-output-translations (:root)
>>           (:current-directory :implementation-type))
>>
>> ?
>>
> More like
> 
> (asdf:initialize-output-translations
>  `(:asdf-output-translations
>     (:root (,(truename *default-pathname-defaults*) :implementation-type))))

What happens to this as the value of *default-pathname-defaults* changes
over time?

I guess I don't understand the role of the (truename
*default-pathname-defaults*) here.

Does this mean that A-O-T by default always does the equivalent of
*centralize-binaries* in A-B-L?

> 
> or if you want to only redirect output for what's in
> the current self-contained directory, and want it to
> be inside a predictable subdirectory thereof, you can use:
> 
> (let ((cwd (truename *default-pathname-defaults*)))
>   (asdf:initialize-output-translations
>    `(:asdf-output-translations
>       (,cwd (,cwd "asdf-output" :implementation-type)))))

Question:  for people who have been using ASDF-BINARY-LOCATIONS for a
while without a deep understanding (e.g., colleagues of mine who just
did what I told them to), would it be possible to provide

(ASDF:ABL-COMPATIBILITY-MODE)

as an alias for the former?

That would allow an easy

#+ASDF2
(ASDF:ABL-COMPATIBILITY-MODE)
#-ASDF2
(ASDF:OOS 'ASDF:LOAD-OP :ASDF-BINARY-LOCATIONS)

in lisp init files.