OK, these are cleaned up. None of them was essential.<br><br><div class="gmail_quote">On Wed, Feb 22, 2012 at 5:32 AM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
hi guys,<br>
<br>
the symlinks causing annoying troubles on windows, since windows have<br>
no support for them.<br>
It is not something which we cannot fix or just ignore, but to my<br>
opinion, in overall, putting symlinks into multi-platfrom project<br>
tracked by source control system is bad idea.<br>
<br>
Here the errors reported by tar (on windows) by unpacking sources,<br>
which previously were dl-ed from scm and tar-ed on linux machine:<br>
<br>
+ tar -xzf cog.tar.gz<br>
tar: cog/macbuild/resources/OpenAL.framework/Resources: Cannot create<br>
symlink to `Versions/Current/Resources': No such file or directory<br>
tar: cog/macbuild/resources/OpenAL.framework/OpenAL: Cannot create<br>
symlink to `Versions/Current/OpenAL': No such file or directory tar:<br>
cog/macbuild/resources/OpenAL.framework/Headers: Cannot create symlink<br>
to `Versions/Current/Headers': No such file or directory<br>
tar: cog/macbuild/resources/OpenAL.framework/Versions/Current: Cannot<br>
create symlink to `A': No such file or directory<br>
tar: cog/nscogbuild/cygwinbuild/installer/onebuild: Cannot create<br>
symlink to `/Users/eliot/Newspeak/closurevm/onebuild/': No such file<br>
or directory<br>
<br>
(the last one is fun because we know who to blame for it ;)<br>
<br>
to my thinking, if to build things some parts cannot live without<br>
symlinks, they should be created by makefiles, or by "configure"<br>
script. But sources should be clean of symlinks,<br>
because they turning a simple tree layout into a graph (often with<br>
loops) making navigation horrifying and confusing many tools, even on<br>
unix:<br>
<br>
find: Symbolic link<br>
`/builds/jenkins/workspace/Pinocchio/../../workspace/Cog-Unix/cog/unixbuild/third-party/alsa-lib-1.0.17a/include/alsa'<br>
is part of a loop in the directory hierarchy; we have already visited<br>
the directory to which it points.<br>
find: Symbolic link<br>
`/builds/jenkins/workspace/Pinocchio/../../workspace/Cog Git Tracker<br>
(blessed)/cog/unixbuild/third-party/alsa-lib-1.0.17a/include/alsa' is<br>
part of a loop in the directory hierarchy; we have already visited the<br>
directory to which it points.<br>
find: Symbolic link<br>
`/builds/jenkins/workspace/Pinocchio/../../workspace/StackVM-Unix/cog/unixbuild/third-party/alsa-lib-1.0.17a/include/alsa'<br>
is part of a loop in the directory hierarchy; we have already visited<br>
the directory to which it points.<br>
find: Symbolic link<br>
`/builds/jenkins/workspace/Pinocchio/../../workspace/MooseOnMoose2/cache/MooseOnMoose2/MooseOnMoose2'<br>
is part of a loop in the directory hierarchy; we have already visited<br>
the directory to which it points.<br>
find: Symbolic link<br>
`/builds/jenkins/workspace/Pinocchio/../../workspace/Nautilus Without<br>
RPackage/cache/Nautilus Without RPackage/Nautilus Without RPackage' is<br>
part of a loop in the directory hierarchy; we have already visited the<br>
directory to which it points.<br>
find: Symbolic link<br>
`/builds/jenkins/workspace/Pinocchio/../../workspace/Cog Git Tracker<br>
(cog-osx)/cog/unixbuild/third-party/alsa-lib-1.0.17a/include/alsa' is<br>
part of a loop in the directory hierarchy; we have already visited the<br>
directory to which it points.<br>
<font color="#888888"><br>
<br>
--<br>
Best regards,<br>
Igor Stasenko.<br>
</font></blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div><br>