Re: resolution of symlinks in asdf

Kevin Layer <[email protected]> writes:

> I added an option for getting around this behavior, :resolve-symlinks.
> The changes are backward compatible--no existing program will break
> due to the additional option.
>
> Attached is a diff -u with respect to 1.97.  Can someone on the commit
> list do the deed?

This may be expedient, but I don't think it makes sense conceptually:
the location that the binary files end up at is not a property of the
system, it is a property of the site policy: as you have in fact
implicitly observed by the fact that your contractor presumably had a
working system, but when integrated in your site's filesystem it
didn't do what you wanted.

I don't know whether this is possible or not, but I think that what
should happen is that your site with the symlink farms should define
output-files methods in your site init files to place the binaries in
appropriate places.  (It may, of course, be that there isn't enough
information around by the time the output-files method runs to put
them in the right place, in which case we'll need to talk again.)

Cheers,

Christophe