[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#850943: [Dose-devel] Bug#850943: dose-builddebcheck: please add an option to check non-full builds



Hi,

Quoting Ralf Treinen (2017-01-11 21:19:25)
> On Wed, Jan 11, 2017 at 02:15:26PM +0100, Johannes Schauer wrote:
> > currently, dose-builddebcheck can only check build dependency
> > satisfiability for full package builds. It would be great if
> > dose-builddebcheck could easily be used to also check arch-all-only,
> > arch-any-only, source-only build or any combination of those.  Specifically
> > this would be interesting for wanna-build because that still has to mangle
> > build dependencies in the right way before passing them to
> > dose-builddebcheck because of this missing feature.
> > 
> > My idea would be to add a new option to dose-builddebcheck like:
> > 
> >  --deb-build=type
> > 
> > Where type is a comma separated value equal to syntax and semantics as
> > for the --build option in dpkg-buildpackage.
> Sounds like a good idea.

cool!

> However, I have no idea what a source-only build is, and how one can obtain
> its build-dependencies.

The idea is to replicate the dependency satisfaction logic that
dpkg-checkbuilddeps uses.

If you say --build=source then it will only evaluate the contents of
Build-Depends and Build-Conflicts (and not Build-Depends-Indep,
Build-Conflicts-Indep, Build-Depends-Arch or Build-Conflicts-Arch).

We have --deb-drop-b-d-indep but that only allows differentiating between full
and arch-all-only builds. We could also add --deb-drop-b-d-arch but using the
--deb-build=type interface I proposed above would:

 - make the dose-debbuildcheck call closer to what one would use with
   dpkg-buildpackage and thus easier to remember
 - avoid having to memorize which --deb-drop-b-d-* option is for which type of
   build

If we would instead add a --deb-drop-b-d-arch option, then the mapping from
dpkg-buildpackage to dose3 options would be as follows:

dpkg                dose3

--build=source      --deb-drop-b-d-arch --deb-drop-b-d-indep

--build=any         --deb-drop-b-d-indep

--build=all         --deb-drop-b-d-arch

--build=binary      (none)

--build=full        (none)

So a disadvantage of a --deb-build=type option would be that the "binary" and
"full" arguments would be functionally equivalent. This would be an argument to
use the --deb-drop-b-d-arch variant instead.

cheers, josch

Attachment: signature.asc
Description: signature


Reply to: