Re: Source-Depends implementation
Ben Collins <firstname.lastname@example.org> writes:
> > > > > All it does is included the Source-Depends field into the
> > > > > .dsc file. This can later be used by apt or dbuild/buildd
> > > > > to verify that all needed packages are installed for
> > > > > building.
> > > >
> > > > sbuild already does this... (with it's own source
> > > > dependencies generated from the dependencies of the binary
> > > > package(s) of the source package and manually added source
> > > > dependencies).
> > >
> > > This doesn't solve necessary binaries used in the make and build
> > > process does it?
> > Yes it does, as those are added by hand.
> That does little more than what we do now...and not everyone who
> wants this feature, wants to do manual adding, otherwise they
> wouldn't need it any way.
a) If you bothered to look at what the automatic src-dep generator
produces, your claim that it `does little more than what we do now' is
b) manual adding _is_ still a major bonus, because it's `add once and
it'll be checked automatically for all future builds'.
c) You *can not* avoid manual additions for any sane and proper system
of source dependencies. But in the rush to implement, something,
anything (a hack, if you will), people don't seem to care about the
> That's an impressive number, but it still has nothing to do with
What like constraints have nothing to do with source dependencies?
Uh, no, it has quite a lot to do with this, and if you didn't want it
mentioned, you shouldn't have brought it up in the first place (you
mentioned buildd, not me).