Re: Re: namespace-deploy-map

Harlan asks:

> Does this mean that if a package has a
>  user-visible target of:	  then it will really be written to:
>  /our/whatever		      /.-ark-deploy-root/whatever
>  /usr/local/whatever	      /usr/local/.-ark-deploy/whatever
>  /whatever		      /.-ark-deploy-root/whatever
> 
> (where "whatever" is a file name, not a directory or a longer path, or
> maybe the search algorithm is "smart".)

(Ah, for 15 mins looking into the same emacs window...)

The table is

  /our/whatever		      /.-ark-deploy/<pkg-id>/whatever
  /usr/local/whatever	      /usr/local/.-ark-deploy/<pkg-id>/whatever
  /whatever		      /.-ark-deploy-root/<pkg-id>/whatever

For example:

  # reveal->deploy
  /our/bin/xemacs -> /.-ark-deploy/xemacs--21.1.14/bin/xemacs

  # deploy->install
  /.-ark-deploy/xemacs--21.1.14 -> /d/.-ark-install-sparc-solaris2.6/xemacs--21.1.14

Note, however, it doesn't *have* to be a symlink; e.g.

  % ls -li /usr/local/bin/python /usr/local/.-ark-deploy/python--2.0/bin/python 
  26501 -rwxr-xr-x   2 matt     csstaff  5173228 Feb 27 00:12 /usr/local/.-ark-deploy/python--2.0/bin/python*
  26501 -rwxr-xr-x   2 matt     csstaff  5173228 Feb 27 00:12 /usr/local/bin/python*

(That's what <deployment-spec> and <revelation-spec>
control.)

Where did I fail to document the above properly?

Will