sshfs doesn't support hard links.  This means that the source tarball
cannot be safely extracted on sshfs filesystems.  Is there any reason
to have these hard links in the source tarball?  The files in question
get re-compiled at build time anyway (when TeX is installed).

$ grep $PWD /proc/mounts
fs:Desktop/darcs /home/twb/Desktop/darcs fuse.sshfs rw,nosuid,nodev,user_id=1187,group_id=2000,max_read=65536 0 0
$ tar zxf darcs-2.0.1rc1.tar.gz
tar: darcs-2.0.1rc1/doc/manual/img6.png: Cannot hard link to `darcs-2.0.1rc1/doc/manual/img4.png': Function not implemented
tar: darcs-2.0.1rc1/doc/manual/index.html: Cannot hard link to `darcs-2.0.1rc1/doc/manual/darcs.html': Function not implemented

So, if I understand correctly, the only thing that goes wrong here is that tar
gives you some warnings when you extract the source tarball.  Is that correct?

If so, I'm marking this as wont-fix.  I tried looking in the tar man page for
options that would make it ignore hard links (and just create a new file), but
didn't find anything.  Also, I'm not too sure what's generating these links in
the first place (latex2html ?) and what parts of the makefile we'd need to fix.

make dist seems to say it uses darcs dist... which suprises me, because darcs
dist only copies recorded files, as far as I know.

Feel free to work on this and report back, of course.  And thanks for the bug
report!

On Thu, Jun 05, 2008 at 07:27:42AM -0000, Eric Kow wrote:
> So, if I understand correctly, the only thing that goes wrong here
> is that tar gives you some warnings when you extract the source
> tarball.  Is that correct?

I'm not sure exactly what tar ends up producing; I just gave up and
ran tar on the remote host (I'm using sshfs in the first place so I
can edit files with Emacs, since TRAMP no longer has multihop.)

> If so, I'm marking this as wont-fix.

No worries.  This is a very low-priority issue as far as I'm concerned.