For symlinks, that won't work unless the sourcedir is absolute, or calculated properly relative to the destdir. I don't see a disclaimer there for that, so I imagine people will be using it naively in a broken way.

For example, the following won't work: 

$ mkdir src dst
$ touch src/foo
$ ln -s src/foo dst/bar

[download]
It doesn't work because the kernel will be trying to find dst/src/foo when dst/bar is referenced. The symlink actually needs to be created non-intuitively as: 
$ ln -s ../src/foo dst/bar

[download]
Perhaps if your code computed the proper relative path from an apparent relative path for symlinks, it'd be more useful.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

In reply to •Re: Crosslink by merlyn
in thread Crosslink by BrentDax

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.