> On Tuesday 21 February 2012 05:12:16 pm Timothy Pearson wrote:
>> > On Tuesday 21 February 2012 04:51:26 pm Timothy Pearson wrote:
>> >> >> On 02/21/2012 02:49 PM, Timothy Pearson wrote:
>> >> >> > The only reason I haven't compiled into Ubuntu<  Oneiric is that
>> it
>> >> is
>> >> >> > only available as a package in Oneiric and up.
>> >> >
>> >> > As long as it doesn't introduce any issues, and as long as it can
>> >> coexist
>> >> > with normal libjpeg, why not compile a version for TDE just for the
>> >> > distros/versions that don't already have it?
>> >> >
>> >>
>> >> It seems to require multilib, and I don't want to get into
>> repackaging
>> >> it
>> >> (due to my perpetual lack of time).
>> >
>> > I meant starting with R14 :-)
>> >
>> > I've never heard of something requiring multilib, nor should it if
>> it's
>> > build on x86, since anything compiled on there is basically "monolib"
>> > anyway.
>>
>> The way they did the libturbo packages ensures that they won't build on
>> anything less than oneiric.  All I know is that it relies on the
>> /usr/lib-<archname>/ structure.
>
> If that's just the Ubuntu package of libjpeg-turbo (not the normal
> libjpeg-turbo), that makes more sense. I've seen quite a few things in
> Ubuntu where I couldn't figure out their reasoning.

Yes, the Ubuntu package is what I am referring to.  Sorry if I was not
clear. :-)

TDE will detect if the libjpeg-turbo package is available on Ubuntu/Debian
and compile against it if it is.

Tim