Re: native packages
On 1/23/07, Neil Williams <firstname.lastname@example.org> wrote:
On Tue, 23 Jan 2007 21:45:44 +1100
"Andrew Donnellan" <email@example.com> wrote:
> In this particular project I am a member of upstream (packager,
> proofreader and copywriter for English website) and I want to store my
> debian/ directory in upstream's SVN as it makes it much easier for me
> to manage snapshots, updates, and so on.
I do the same, many other DD's too.
The simple solution is this:
Keep the debian/* files in CVS/SVN.
Don't package the debian/* files in the distributed tarball.
When building the packages, you simply download the released tarball as
usual, copy your debian/* files into place and build. You retain all
the advantages of building the unreleased code for test packages direct
> If debian-native packages are discouraged then is there a good way to
> keep the debian/ dir with upstream's VCS?
You can do whatever you like as long as the debian/ directory is NOT
part of the released tarball.
Thanks for the advice; I've just put together a shell script to do all
this for me. Should this produce a native package?
svn update jabbin/
REVISION=`svn info jabbin/ | grep "Revision" | cut -f 2 -d " "`
cp -r jabbin $DIR
find | grep "\.svn" | xargs rm -rf
mv debian/ patches/ ../tmp$DIR
tar cvzf $DIR.orig.tar.gz $DIR
mv ../tmp$DIR/* .
dch -v $VERSION
dpkg-buildpackage -sa -rfakeroot
ajdlinuxATgmailDOTcom (primary) ajdlinuxATexemailDOTcomDOTau (secure)
firstname.lastname@example.org hkp://subkeys.pgp.net 0x5D4C0C58
Get free rewards - http://ezyrewards.com/?id=23484