Matt Massie wrote:
People who want to modify and develop the C code, could use 'src/c' in the
tarball or use svn directly. However, people who just want to simply
use/consumer the C implementation without any hassle would use the
avro-c-x.x.x.tar.gz package. Package maintainers would also use this
pristine tarball as a basis for packaging as well.
Could avro-c-x.x.x.tar.gz be created by the following?
tar xzf avro-x.x.x.tar.gz src/c
cd src/c
tar czf ../../avro-c-x.x.x.tar.gz
I don't see why it shouldn't be, and, if it can be, I don't see why we
needthe nested tarball: we ship a single pristine tarball, and folks can
re-package parts of it as needed. What am I missing?
Doug
