Le 29/10/2013 15:48, Stefan Dirsch a écrit : > On Tue, Oct 29, 2013 at 03:40:09PM +0100, Guillaume Gardet wrote: >> Le 17/10/2013 11:51, Stefan Dirsch a écrit : >>> On Thu, Oct 10, 2013 at 03:24:39PM +0200, Guillaume Gardet wrote: >>>> Le 10/10/2013 14:03, Stefan Dirsch a écrit : >>>>> On Wed, Oct 09, 2013 at 04:43:59PM +0200, Guillaume Gardet wrote: >>>>>> Le 19/09/2013 15:28, Guillaume Gardet a écrit : >>>>>>> Le 19/09/2013 15:21, Stefan Dirsch a écrit : >>>>>>>> On Wed, Sep 18, 2013 at 12:27:07PM -0500, Alexander Graf wrote: >>>>>>>>> Am 18.09.2013 um 06:48 schrieb Guillaume Gardet >>>>>>>>> <[email protected]>: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> raspberrypi-gfx and mesa provide openGL ES libs and devel files. So, >>>>>>>>>> there are file conflicts. Should we add a "Conflicts:" line in >>>>>>>>>> raspberrypi-gfx spec file? >>>>>>>>>> >>>>>>>>>> Or is there a better way to avoid problems? >>>>>>>>> Let's ask someone with a clue :). Stefan, do you have any ideas here? >>>>>> ping >>>>>> Guillaume >>>>>> >>>>>>>> Where can I find the sources for the raspberrypi-gfx package? >>>>>>> In raspberrypi-firmware package since it is the same sources. >>>>>>> >>>>>>> I think we should split raspberrypi-gfx in subpackages (*-libGLESv2, >>>>>>> *-libEGL, etc.) as in Mesa. >>>>> I didn't receive this reply. Most likely, because it has only been >>>>> addressed >>>>> to the ML, which I'm not subscribed to. >>>>> >>>>> But, yes. Splitting the package up like it is done in Mesa would be the >>>>> first >>>>> step. BTW, I still can't find that package anywhere. Apparently it isn't >>>>> on >>>>> the openSUSE buildservice. >>>> You can find it here and there for Factory and 13.1 : >>>> https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryPi/raspberrypi-firmware >>>> https://build.opensuse.org/package/show/devel:ARM:13.1:Contrib:RaspberryPi/raspberrypi-firmware >>> Thanks! >> Did you have some time to have a look at it? > Not at all. I won't before my vacation either. But why do I need? Just make > sure you have some special package selection for the raspberrypi distribution > (no idea how this is handled though) and let the raspberrypi packages > provide/obsolete the appropriate Mesa packages, so you don't have conflicts.
Ok. This is where I am not sure how to handle it correctly. How should I use "provide" and/or "obsolete" here? Is there any other package which provides same libs as Mesa, so that I take it as a template? Or any other packages providing libraries with the same names. Something like: Provides: Mesa-libGLESv2 is enough to not have install/deps conflicts? Should I add: Obsoletes: Mesa-libGLESv2 ? Is there any problem to provide and obsolete the same package? Guillaume > > I hope there won't be any changes needed for Mesa packaging. > > Thanks, > Stefan > > Public Key available > ------------------------------------------------------ > Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH > Tel: 0911-740 53 0 Maxfeldstraße 5 > FAX: 0911-740 53 479 D-90409 Nürnberg > http://www.suse.de Germany > -------------------------------------------------------------- > SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix > Imendörffer, HRB 16746 (AG Nürnberg) > -------------------------------------------------------------- > -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
