[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The drawbacks of the --symlink option
From: |
Ralf Wildenhues |
Subject: |
Re: The drawbacks of the --symlink option |
Date: |
Mon, 9 Oct 2006 14:34:29 +0200 |
User-agent: |
Mutt/1.5.13 (2006-09-08) |
Hello Bruno,
* Bruno Haible wrote on Mon, Oct 09, 2006 at 02:25:24PM CEST:
> gnulib-tool's --symlink option [...]
> 2) "tar cfvz" creates a tarball which is not self-contained. It happened
> twice to me today: I created a tarball of coreutils, transferred it to
> another system for testing, and it didn't work because the symlinks
> which point to a partition not available on that other system.
> 3) Other manipulations a maintainer normally does (chmod -R or others)
> might not work well with symlinks.
Both of these are solved by
make dist
I don't think I ever create tarballs any differently (I have no
intention to pack some src/srcfile-changed.c that doesn't belong in the
tarball), and I get mildly upset if a maintainer thinks this target is
reserved for him alone, i.e., by requiring cvs write access to succeed.
Cheers,
Ralf