On 17 April 2017 at 10:57, Björn 'besser82' Esser < besser82@fedoraproject.org> wrote:

why would you want to do this? I cannot imagine any real use-case for something like that…

If only package X with version greater than N and release M has has some fixes which allows to build your package such BR has sense. And yes .. it is possible to add in BR version and release.

kloczek

Sorry that I just missed the emails...

On Mon, Apr 17, 2017 at 7:26 PM, Tomasz Kłoczko kloczko.tomasz@gmail.com wrote:

On 17 April 2017 at 10:57, Björn 'besser82' Esser < besser82@fedoraproject.org> wrote:

...

why would you want to do this? I cannot imagine any real use-case for something like that…

If only package X with version greater than N and release M has has some fixes which allows to build your package such BR has sense. And yes .. it is possible to add in BR version and release.

When change a package's compile options or add some tweak patches, IMO, it's better to change the Release version only.

On Mon, Apr 17, 2017 at 11:19 PM, Stephen Gallagher sgallagh@redhat.com wrote:

On 04/17/2017 02:35 AM, xiaofeng wrote:

...

Hi all,

Is it possible to define BuildRequires on version with release number?

Which release number do you mean? The value in the "Release:" field of the spec file? Or do you mean the Fedora release version (such as "25")?

In the former case, you can just specify:

BuildRequires: foo > 1.0.0-4

That's what I want.

In the latter case, you probably want:

%if 0%{?fedora} >= 25 BuildRequires: foo %else BuildRequires: bar %endif _______________________________________________ packaging mailing list -- packaging@lists.fedoraproject.org To unsubscribe send an email to packaging-leave@lists.fedoraproject.org