Re: Does pbuilder need to be run for each build?
On Tue, Oct 12, 2010 at 05:10:10PM -0500, Misha Koshelev wrote:
> Is the typical protocol to do pbuilder, or is it just to use svn-buildpackage?
You should use pbuilder at least once to make sure the
Build-Dependencies are valid. Otherwise you can do whatever build tool
you prefer. That becomes pretty clear if you consider that *your*
package will (at least as long as you did not become a Debian
Maintainer) never propagate to an offical debian.*org* server (just
mentors.debian.*net*). The final upload has to be done by a sponsor
(for instance me) and the sponsor will rebuild the package anyway (if he
is doing a proper job). So just do what might fit your workflow the
best and make sure you are using pbuilder at least once to save the
sponsor some unwanted surprise.
BTW, there are people who prefer cowbuilder which is using pbuilder with
Copy-On-Write (=COW) which is faster. I personally decided that the
installation of cowbuilder (which was known to be a bit complicated in
the past - this might have changed) would perhaps cost me more time than
waiting for pbuilder to work.
So whatever you use: The important thing is that the result is a proper
debian/ directory in SVN which enables the sponsor to use it to build
the orig.tar.gz tarball into a lintian clean package.
Kind regards and thanks for your careful work on this
Andreas.
--
http://fam-tille.de
Reply to: