Re: getting rid of the .changes requirements
Stig Sandbeck Mathisen <ssm@debian.org> writes:
> On Sun, Jun 23, 2013 at 12:41:01PM -0400, micah wrote:
>> Could you describe how it is painful or non-trivial? It isn't that I
>> disagree with you, I just simply do not see it because it is quite
>> easy for me to do and I'm curious to know in what situations that is
>> difficult.
>
> While you're at it, how do you make it easy? :)
For backports, I've been using a rather old script that Russ Allbery
wrote[0]. This along with cowbuilder setup to build things for multiple
distributions[1] makes the whole thing pretty simple (at least for
simple backports).
> I always build a .dsc using "gitpkg", and then build that in a clean
> environment, usually with "pbuilder-dist", "pbuilder", or
> "sbuild". (Alternatively, test it automatically with autopkgtest,
> piuparts and lintian)
Personally, I prefer to use the testing package itself, rather than
recreate it from a git repository. Less chance of screwing up and doing
something different than what is in the testing repository.
micah
0. http://www.eyrie.org/~eagle/journal/2013-05/002.html
1. http://wiki.debian.org/cowbuilder#Building_your_package_for_many_distributions_at_once
Reply to: