"non-local" components in asdf

hello;

i am contemplating supporting asdf for the next cl-xml release. most 
likey in the form of macros which rewrite the system management 
expressions which i inherited from cl-http.

i don't understand how to succinctly express non-local components. is 
there a way to do this, or does asdf argue against them? by "non-local" 
i mean a file component which is not in the directory designated by the 
path in effect for its module. i tried to just go ahead and give such a 
component a relative pathname as a name, but that did not have the 
desired effect.

...



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com