>>> yes - that's same issue; I did delete my source tree, and extracted from >>> MSYS with: >>> tar xfhz openssl-1.0.0b.tar.gz >> Is it correctly understood that in this context 'h' option simply omits >> symbolic links? I get a bunch of "Cannot create symlink to" with >> corresponding consequences. Configure then "recreates" them by copying >> files symlinks should point to. Can you confirm this? A. > nope. See: > http://linux.die.net/man/1/tar > -h, --dereference > don't dump symlinks; dump the files they point to > > I dont see what you describe; but some more tests on MSYS show that it > works also correctly even when I extract the release archive with > standard command: > tar xfz openssl-1.0.0b.tar.gz
My MSYS is older... What I can tell about it is that 'ln -s' "works" by *copying* the file to target location. Or should I say "pretends working". Your tar might do the same, i.e. defer symlink "resolution" till the end of tar-file and copy the files. Can you confirm this? It should be noted that Vista and onward implements symbolic links, and it's not impossible to imagine that new enough MSYS would take advantage of it:-) > also did just some tests on Linux, and it seems that -h does only work > for archiving, but not extracting: > tar xfz openssl-1.0.0b.tar.gz > tar cf openssl-1.0.0b.tar openssl-1.0.0b/ > tar chf openssl-1.0.0b-h.tar openssl-1.0.0b/ > ll *.tar > -rw-r--r-- 1 root root 21575680 Nov 20 03:15 openssl-1.0.0b-h.tar > -rw-r--r-- 1 root root 19793920 Nov 20 03:15 openssl-1.0.0b.tar Right, this was exactly suggestion in #2273. I.e. re-pack resolving symbolic links. Either way, shall we settle for http://cvs.openssl.org/chngview?cn=20071. Cheers. A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
