I'm currently working to package pieces of the NetBSD source tree (little things like libc12, for instance). Because the full source tree is vast, unwieldly, and by and large much of it is not actually useful or needed for the Debian GNU/NetBSD port (for example, the entire gnu/ tree is replaced by Debian packaged software), these packages are generally built based on a partial copy of the relevant parts of the NetBSD CVS tree (currently from the tagged release point release-1-6).
It's easy enough to create an orig.tar.gz:
tar -czvf libc12_1.6.orig.tar.gz libc12-1.6/*.bz2
produces one. However, I run into a problem at this point; future releases
of the package (-2 and above) might well need to pull in different files
or parts of the source tree. This would result in a different orig.tar.gz
file, which seems like it wouldn't work - however, it also seems silly (and
probably confusing) to version it as Debian-native, since there is a clear
versioning point in the upstream sources.
Certainly, it would be possible to tar up the entire tree, 'just to be
safe', but the *compressed* tarball (bzip2 -9 or gzip -9) is close to half
a gig, of which the vast majority is useless.
Please tell me there's a better solution...
--
***************************************************************************
Joel Baker System Administrator - lightbearer.com
[EMAIL PROTECTED] http://users.lightbearer.com/lucifer/
pgpKPV1F3kizK.pgp
Description: PGP signature
