Re: Question regarding min and max dependencies

[Shawn Iwinski <shawn.iwinski@xxxxxxxxx>]

Good idea Rex, but I am not sure that will work for my exact case.  PHP PEAR requires already use virtual pkgs.  Here are a couple real examples I have:

Requires:  php-pear(pear.twig-project.org/Twig) >= 1.0

Requires:  php-pear(pear.twig-project.org/Twig) <  2.0

Requires:  php-pear(pear.doctrine-project.org/DoctrineCommon) >= 2.3.0

Requires:  php-pear(pear.doctrine-project.org/DoctrineCommon) <  2.4.0

On Thu, Mar 7, 2013 at 10:54 AM, Rex Dieter <rdieter@xxxxxxxxxxxx> wrote:

On 03/07/2013 09:47 AM, Shawn Iwinski wrote:

Is it valid to use 2 requires of the same dependency for min / max
versions?  For example, I have a package "foo" that depends on package
"bar" >= 1.0 and also "bar" < 2.0.

I have seen many packages use this:
Requires: bar >= 1.0
Conflicts: bar >= 2.0

but I would like to use the following (which may help with finding
dependencies using repoquery):
Requires: bar >= 1.0
Requires: bar < 2.0

If you have access to modify "bar", I'd suggest one way of tackling issues like this is adding a virtual Provides to bar.spec like:

Provides: bar1 = %{version}-%{release}

So, now you can avoid the above examples you mentioned using just:

Requires: bar1
(versioned or not)

-- rex
--
packaging mailing list
packaging@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/packaging

--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging