[MoM ... inofficial] Packaging ARB
Hi Elmar,
since I have the feeling from private communication that the workflow
for packages in SVN is not explained in full detail I try to repeat *my*
workflow here. Please note: If you prefer Git over SVN I'm fine
with migrating the Arb packaging to git.
Since arb is an existing package you can checkout the packaging via
debcheckout --user <username> arb
(make sure you will not forget the --user option with your user name on
alioth). Since there is a new version of arb anyway it mighht be way
more straightforward to not use debcheckout which also fetches the
current packaging source but rather do
svn checkout svn+ssh://svn.debian.org/svn/debian-med/trunk/packages/arb/
(Plase make sure that you are able to
ssh svn.debian.org
without typing your password but rather use ssh-add on your local
machine as explained in the Wiki.)
To fetch the latest upstream source you can do
cd arb/trunk
uscan --verbose --force-download
which should download the latest arb version.
Please note that *I* *personally* do *not* use svn-buildpackage. I
tried it a long time ago but failed with this. So I simply ignore its
features (in contrast to git-buildpackage which I'm using for Git based
packaging which works 98% nicely). So I'm simply doing:
cd ..
tar xaf <original_tarball>
cp -a trunk/debian <unpack_dir>
cd <unpack_dir>
debuild
This should be the simplest way to create the package. I'm using
actually pbuilder / cowbuilder (which should be sufficiently explained
in the Debian Med policy[1]. When I did some changes in the debian/ dir
I'm using midnightcommander (mc) to compare the differences between my
changes and the status of SVN, copy the files to trunk/debian and commit
these changes. I have no idea whether I should really recommend this
manual workflow over svn-buildpackage but it simply works for me.
If you might continue to have trouble with the build workflow feel fre
to ask here.
Kind regards
Andreas.
[1] http://debian-med.alioth.debian.org/docs/policy.html
--
http://fam-tille.de
Reply to: