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

[Henrik Nordström]

tis 2010-12-21 klockan 09:50 -0700 skrev Kevin Fenzi:

> Basically it's changing spec files BuildRequires to suit our build
> setup and not for 'the version this package needs to build'. 

True. And it's use should be limited to the release branches of a
package, not master/rawhide. 

Imho it adds value in the stable branch, as any lower version than
indicated is not aceptabe for packaging in that branch.


> So, folks who take our src.rpms to rebuild/build elsewhere will find
> this anoying. Also, there's not any easy way to see what the real
> version is... 

A comment as you included should be good enough in most cases I think.

Or if you want to go fancy about it then use
%if 0%{fedora} = 14
BuildRequires: foo-devel >= 1.1.0
%else
BuildRequires: foo-devel
%endif

> This way you can add your override and use it to build what you want,
> but you will be nagged every day to check and remove the override if
> you no longer need it.

The main thing I have against overrides is that they affect a lot more
than just a single build.

Regards
Henrik