[buildd-tools-devel] Bug#714149: sbuild: Let users push additional s to the build dependencies dummy archivearchive

[Geoffrey Thomas]

On Wed, 26 Jun 2013, Emanuele Aina wrote:

> When building related set of packages most people resort to set up a local
> archive to enable the newly built packages to depend on locally built
> dependencies for which the needed version has not hit the main archive yet.
>
> Since sbuild already sets up a dummy archive for build dependencies, it could
> also allow users to specify a list of packages that should be pushed there.
>
> To do so I've added an --add-extra-package option that accepts a debfile and
> can be used multiple times. It already allowed me to locally build packages
> which depend on stuff not yet in the archive without any additional setup.
>
> The git repo (`add-extra-package` branch) with the patches is at
> http://cgit.collabora.com/git/user/em/sbuild/log/?h=add-extra-package
>
> I also took the chance to refactor a bit the dummy archive handling and split
> it out of the ResolverBase class. Even if not strictly needed it allowed me to
> have a clear idea of the involved pieces and I think that the result is a bit
> easier to understand and more flexible.
>
> Comments and suggestions welcome, I'm not very proficient in Perl. :)

Hi Emanuele,

This looks like exactly what I was going for with this much smaller 
patch, written for bug #700522:
https://github.com/geofft/sbuild/commit/3f7ecfde5e07c66ec1d7e88fac7423f94400f68b

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700522

Want to merge these two wishlist bugs? I haven't looked in detail at your 
refactoring, but it felt like my patch was adding this in a slightly 
questionable manner, so I'd be happy for yours to get merged instead if 
it's preferable.

Also want to take a crack at --add-repository? :-) My plan there was to 
patch `apt-get update` to let you update a single repository, clean up the 
existing messy code that you refactored into force_update_archive_list() 
to use that interface, and then allow adding a sources.list.d file and 
updating that. Unfortunately the most obvious way to implement that apt 
patch ends up with apt forgetting about every other source, and I didn't 
have time to try harder.

-- 
Geoffrey Thomas
gthomas at mokafive.com