[packager interface suggestion] Adding packages to buildroot directly from updates-testing

[seth vidal]

On Mon, 2010-12-20 at 15:58 -0500, seth vidal wrote:
> On Mon, 2010-12-20 at 21:55 +0100, Henrik Nordström wrote:
> > fre 2010-12-17 klockan 11:22 +0100 skrev Michael Schwendt:
> > 
> > > +1 to some way of automating koji buildroot overrides (perhaps based
> > > on FAS group membership such as provenpackagers) in order to remove
> > > the releng bottleneck.
> > 
> > Suggestion on how to express this in the packaging process:
> > BuildRequires with a version requirement pulling in from updates-testing
> > if the required version can not be satisfied from the stable repository.
> > 
> > Will need some yum coding in using fallback on updates-testing or other
> > selected fallback repositories on dep failures. Something I think is
> > interesting for other activities as well.
> > 
> > This way the packager need to explicitly request the newer version in
> > the spec file to have it included in the build root, and builds are also
> > reproducible and self-contained with no sideband dependency requirements
> > outside the spec file.
> > 
> 
> So you want contingency fall-through deps?
> 
> ie: BuildRequires: foo = 1.1.1 (but if that's not available foo =
> 1.0.0)?
> 
> How is that interesting other than making it possible to replicate the
> build environment?

interesting typo: s/possible/impossible/

-sv