Hi Yaroslav, On Mi 20 Mär 2013 20:26:24 CET Yaroslav Halchenko wrote:
On Sat, 16 Mar 2013, Mike Gabriel wrote:Hi Yaroslav,On Fr 01 Mär 2013 16:11:10 CET Yaroslav Halchenko wrote:>Hi Guys,>I wonder if anyone could give a concise summary stopping libjpeg-turbo >from being uploaded? there seemed to be lots of work, clarifications >from upstream, downstream distributions including it,... and no >clarity why we do not have it in Debian yet (could simply be a lack of >time?).>Thank you in advance!I have experimented around with libjpeg-turbo.git on collab-maint recently.I have updated upstream to 1.2.90.By now the current version already looks quite promosing (I hope). The dpkg-divert stuff, I have remove. The current policy is:o link native libjpeg-turbo code against libturbojpeg1 -> a package like TigerVNC or VirtualGL should use libturbojpeg1 o if the system admin chooses to replaced libjpeg8 by libjpeg8-turbo, he/she may do so. Only then libjpeg8 is replaced (including all consequences for all applications on the system)I think Conflicts/Replaces should be cleaned-up for the libjpeg8-turbo Package: libjpeg8-turbo Architecture: any Multi-Arch: same Section: libs Pre-Depends: multiarch-support Depends: ${shlibs:Depends}, ${misc:Depends} Conflicts: libjpeg62, libjpeg7 Replaces: libjpeg62, libjpeg7, libjpeg8 (<< 9) Provides: libjpeg8 Description: IJG JPEG compliant runtime library - SIMD optimized This library is based on libjpeg-turbo and not on the IJG JPEG. . This package provides the runtime library supporting the Independent JPEG Group's standard for JPEG files. . WARNING: This package contains a shared library which is a drop in replacement for libjpeg8. Replacing the standard libjpeg6 library may have unexpected/unknown effects on certain applications. atm it conflicts with libjpeg62 libjpeg7 but doesn't actually provide them, thus resulting in need to remove a bulk of packages happen I decide to give libjpeg8-turbo a shout as a replacement for libjpeg8. So why there are those Conflicts: and Replaces for the lib package?
Agreement from here. I guess the different libjpegXX Conflicts:/Replaces: relates to the historical arising of the different compat levels available in libjpeg-turbo.
Also, the earlier package versions did not conflict+replace, they played around with dpkg-divert and allowed simultaneous installation of libjpeg8 and libjpeg8-turbo. Only with the last packaging efforts I changed it over to Conflicts:/Replaces:. So it might have been me, you did some unlean control file editing.
Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
Attachment:
pgpUo8lP8CDik.pgp
Description: Digitale PGP-Unterschrift