On Sat, Nov 7, 2009 at 11:00 PM, Dr. David Kirkby
david.kir...@onetel.net wrote:
But how did you find out these two were hard links? I'm not aware of any way
to
find if A is a hard link of B, unless one finds the inodes and compares them,
which would be next to impossible where there are a
On Sat, Nov 7, 2009 at 11:00 PM, Dr. David Kirkby
david.kir...@onetel.net wrote:
Gonzalo Tornaria wrote:
Is it really necessary for sage-bdist to preserve hardlinks?
[ ... checking a bdist tarball of 4.1.1 ... ]
there is exactly one hardlink in this bdist tarball:
local/bin/python is a
2009/11/8 Gonzalo Tornaria torna...@math.utexas.edu:
On Sat, Nov 7, 2009 at 11:00 PM, Dr. David Kirkby
david.kir...@onetel.net wrote:
But how did you find out these two were hard links? I'm not aware of any way
to
find if A is a hard link of B, unless one finds the inodes and compares
On Sun, Nov 8, 2009 at 9:31 PM, David Kirkby david.kir...@onetel.net wrote:
Hopefully, -pR may work for any POSIX system if the reason for the
hard link is known. I can't see what creates that link myself. You
clearly have a much greater understanding of the issues than me.
Just to clarify,
Do we know why the '-L' option is used once?
cp -L$OPT devel/sage-main $TMP/devel/sage-main
I read the POSIX standard, and although this is a required option, I can't
really work out exactly what the option is supposed to do. To quote from the
2004 standard:
On Sat, Nov 7, 2009 at 6:48 AM, Dr. David Kirkby
david.kir...@onetel.net wrote:
cp -L$OPT devel/sage-main $TMP/devel/sage-main
Maybe this is done to handle the case where sage-main is a symlink
to an actual directory. The option -L means to copy symlinks as real
files. Otherwise, the symlink may
Gonzalo Tornaria wrote:
On Sat, Nov 7, 2009 at 6:48 AM, Dr. David Kirkby
david.kir...@onetel.net wrote:
cp -L$OPT devel/sage-main $TMP/devel/sage-main
Maybe this is done to handle the case where sage-main is a symlink
to an actual directory. The option -L means to copy symlinks as real
