[Rpm-ecosystem] Requires based on destination hardware

[Igor Gnatenko]

Platform I'm targeting support is F23+ so yes, but my solution looks
better. Otherwise once I will add one more implementation I should update
all packages..

On Sat, Dec 12, 2015 at 7:23 PM Neal Gompa <ngompa13 at gmail.com> wrote:

> On Sat, Dec 12, 2015 at 1:19 PM, Igor Gnatenko
> <i.gnatenko.brain at gmail.com> wrote:
> > It is already implemented, but I'm thinking how to make better
> dependencies
> > on opencl realizations. For example, we have program which uses OpenCL,
> but
> > how we can provide to user one of implementations of OpenCL? First idea
> > which comes to my mind to make Provides: opencl to all implementations
> and
> > Requires: opencl in this program, but it is not looks very good..
> >
>
> Does the platform you're targeting support the new rich dependencies?
> If so, you could use that.
>
> For example:
>
> Requires: (opencl-imp1 or opencl-imp2 or opencl-imp3)
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> _______________________________________________
> Rpm-ecosystem mailing list
> Rpm-ecosystem at lists.rpm.org
> http://lists.rpm.org/mailman/listinfo/rpm-ecosystem
>
-- 

-Igor Gnatenko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-ecosystem/attachments/20151212/5904064d/attachment.html>