[ptxdist] How to deal with "alternatives"

[ptxdist] How to deal with "alternatives"

[Erwin Rol]

Hey all,

I was wondering how I can deal with "alternatives" packages?
I have a nVidia BLOB driver for Tegra 2 OpenGL ES. That drivers brings 
the OpenGL libs that are needed by 3d programs. But those programs all 
"select" MESALIB which brings the opensource OpenGL libraries.

So how can I deal with two (or more) packages that offer feature XYZ 
that is needed by other packages?

- Erwin


-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] How to deal with "alternatives"

[Michael Olbrich]

Hi,

On Sun, Feb 05, 2012 at 11:18:10PM +0100, Erwin Rol wrote:
> I was wondering how I can deal with "alternatives" packages?
> I have a nVidia BLOB driver for Tegra 2 OpenGL ES. That drivers
> brings the OpenGL libs that are needed by 3d programs. But those
> programs all "select" MESALIB which brings the opensource OpenGL
> libraries.
> 
> So how can I deal with two (or more) packages that offer feature XYZ
> that is needed by other packages?

There is no generic solution for this. In your case I'd suggest a dummy
mesalib package, that redirects the dependency to your OpenGL package:
A makefile with just "PACKAGES-$(PTXCONF_MESALIB) += mesalib" and an
in-file that selects your package.
However, this won't generate any ipkg dependencies. A solution for this is
on the todo list, but so far not implemented.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de