Bug#612341: bumblebee, libjpeg-turbo: Wheezy does not work well with modern notebook PCs.
Hi there,
On Sat, May 26, 2012 at 8:34 PM, Osamu Aoki <osamu@debian.org> wrote:
> Hi,
>
> On Sat, May 26, 2012 at 06:31:46PM +0200, Mike Gabriel wrote:
>> Hi all,
>>
>> On Sa 26 Mai 2012 17:11:02 CEST Osamu Aoki wrote:
>>
>> >This ITP Bug #612341 was supposed to be closed by Fathi sometime early
>> >January. Nothing happened. http://bugs.debian.org/612341
>> >
>> >In the meantime, Ubuntu package was updated to generate -dev etc.
>> > https://launchpad.net/ubuntu/+source/libjpeg-turbo
>> >
>> >libjpeg-turbo (1.1.90+svn733-0ubuntu4) precise; urgency=low
>> >
>> > * Install jpegint.h in the -dev package.
>> > * Install jconfig.h in the multiarch include directory.
>> > -- Matthias Klose <email address hidden> Fri, 13 Jan 2012 12:02:38 +0100
>> >
>> >This package can be build on sid (under pbuilder) nicely practically as
>> >is and also makes libjpeg-turbo8. So ABI of version 8 is taken care as
>> >I understand.
>> >
>> >Also, Mike Gabriel's work seems to have done somethings interesting on
>> >old Fathi's version and made many improvements.
>>
>> thanks for pinging us! I agree, libjpeg-turbo has to be in Wheezy!!!
>>
>> Fathi, please send us a notice what you plan on this package.
>
> I see Fathi being quite active.
>
> I have made packages for libjpeg-turbo 1.2.0. It builds OK. (Not much
> useful to replace current libjpeg due to conflicts caused with many
> packages. But who cares if it is used in the chroot to build virtualgl
> :-) But I am not really up to maintaining this complicated package.
>
> My build result and git record are here as tar:
> http://people.debian.org/~osamu/libjpeg-turbo-1.2.0-osamu.tar.gz
>
> Since -dev package is the only ones desparatedly needed, ... This is the
> most important thing to get now.
>
> Maybe in post-wheezy, people can discuss transition from libjpeg to
> libjpeg-turbo. This package is very tricky since it tries to replace
> libjpeg.
>
> Regards,
>
> Osamu
>
> CCed: Bill who is libjpeg maintainer.
As far as I know libjpeg is not really concerned here. virtualgl only
links to libturbojpeg. So there really are two issues in a single
report:
1. optimized jpeg lib, as a replacement for libjpeg8
2. getting bumblebeed/virtualgl/turbojpeg(only) in debian
Maybe it would be easier to only focus on (2) ?
2cts
-M
Reply to: