[meego-packaging] Policy regarding non-oss and deps on this
kad at kad.name
Wed Sep 22 03:30:26 PDT 2010
On Wed, Sep 22, 2010 at 09:59, Carsten Munk <carsten at maemo.org> wrote:
> So, at some point we'll be having the ARM OMAP3 SGX (GLES) libraries
> in non-oss. These are typically plug-and-play into a image just like
> pvr-bin (for MRST).
> Now, we have a different problem than MRST. We have a (open source)
> xorg-x11-fbdev-sgx, which depends on libPVR2D, a PowerVR specific
> interface. This is used for hardware acceleration of EXA and such
> giving significant performance benefit (may even be useful on MRST?)
> It's obvious that we can't have non-oss dependencies in Trunk and nor
> do I think we should have.
> The problem is, how do we deal with xorg-x11-fbdev-sgx?
> My initial proposal would be to have it (full source and packaging) be
> in Trunk:non-oss and build against the libPVR2D there, but this is not
> that clean.
As fast solution for 1.1, that is most clean solution within very
For 1.2 we can think and do it better.
> The alternative is writing 'open' stub implementation of libPVR2D and
> putting this in Trunk, but this is even more ugly..
> Or just giving up and only shipping the binaries of xorg-x11-fbdev-sgx
> which is even more evil and would not catch Xorg upgrades as fast as
> How would you (distribution team/handset release engineering) propose
> we proceed with this matter?
br, Alexander Kanevskiy
More information about the MeeGo-packaging