[opensuse-packaging] jpeg packaging
Hi list, I would like to hear your opinion about future jpeg packaging. I am asked to switch back to jpeg6 in Factory. Nowadays we have following packages in graphics project: * libjpeg6 (contains only library) * libjpeg7 (contains only library) * jpeg (contains doc files and bin tools) -> libjpeg8 (contains library) -> libjpeg-devel (contains *.h and *.so) I should do full-fledged jpeg 6 package as jpeg (8) is and we should have it in parallel if I understend correctly (not sure about jpeg 7 package). I would appreciate any advice, here is a first thought proposal: * jpeg6 (contains doc files and bin tools) provides: jpeg, obsoletes: jpeg, conflicts: jpeg8 -> libjpeg6 (contains library) -> libjpeg6-devel (contains development files) provides: jpeg-devel, obsoletes: jpeg-devel, conflicts: jpeg8-devel * jpeg8 (contains doc files and bin tools) conflicts: jpeg6 -> libjpeg8 (contains library) -> libjpeg8-devel (contains development files) conflicts: jpeg6-devel Requires should stay same modulo major version. Other possibility is to let particular project decide, which jpeg should be default (similarly to libpng12,14 in 11.3). Both libjpeg{6,8}-devel would provide jpeg-devel and conflict with otherproviders(jpeg-devel) and similarly for jpeg{6,8}. Petr
2010/12/7 Petr Gajdos
Hi list,
I would like to hear your opinion about future jpeg packaging. I am asked to switch back to jpeg6 in Factory.
Nowadays we have following packages in graphics project: * libjpeg6 (contains only library) * libjpeg7 (contains only library) * jpeg (contains doc files and bin tools) -> libjpeg8 (contains library) -> libjpeg-devel (contains *.h and *.so)
I should do full-fledged jpeg 6 package as jpeg (8) is and we should have it in parallel if I understend correctly (not sure about jpeg 7 package).
jpeg 7 only existed for 6 months, I don't think there is any use for it. But we are already testing this... 11.3 hasn't a libjpeg7 packages, was any bug report created asking for it?
I would appreciate any advice, here is a first thought proposal:
* jpeg6 (contains doc files and bin tools) provides: jpeg, obsoletes: jpeg, conflicts: jpeg8 -> libjpeg6 (contains library) -> libjpeg6-devel (contains development files) provides: jpeg-devel, obsoletes: jpeg-devel, conflicts: jpeg8-devel
* jpeg8 (contains doc files and bin tools) conflicts: jpeg6 -> libjpeg8 (contains library) -> libjpeg8-devel (contains development files) conflicts: jpeg6-devel
Requires should stay same modulo major version.
jpeg6 should be compiled from libjpeg-turbo. But it seems OK to me. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 07/12/10 17:07, Cristian Morales Vega wrote:
jpeg6 should be compiled from libjpeg-turbo. But it seems OK to me.
I prepared libjpeg-turbo package in my home project (home:prusnak / libjpeg-turbo) some time ago. Upstream promised to deliver 1.0.2 soon which will be compatible with both v6 and v8 API, but the project page still has only 1.0.1. If they will indeed release such version, it could help us a lot and save us headache ... -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
2010/12/8 Pavol Rusnak
On 07/12/10 17:07, Cristian Morales Vega wrote:
jpeg6 should be compiled from libjpeg-turbo. But it seems OK to me.
I prepared libjpeg-turbo package in my home project (home:prusnak / libjpeg-turbo) some time ago. Upstream promised to deliver 1.0.2 soon which will be compatible with both v6 and v8 API, but the project page still has only 1.0.1. If they will indeed release such version, it could help us a lot and save us headache ...
Do you mean to provide both v6 and v8 from jpeg-turbo? The problem is http://libjpeg-turbo.svn.sourceforge.net/viewvc/libjpeg-turbo/trunk/README-turbo.txt?revision=305&view=markup says the v7/v8 compatibility will not be complete (and since everybody is starting to use libjpeg-turbo I expect it to never be). IMHO if someone creates a binary linked to libjpeg.so.8 we owe him to have a 100% compatible library. The app will not have the speed boost, but that's something the binary creator should accept if he decides to not link to libjpeg.so.6. So libjpeg.so.8 should be provided from IJG's source. It could be *also* provided from jpeg-turbo so the user can change it if he decides to do so, but that would be unnecessary courtesy. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 08/12/10 18:53, Cristian Morales Vega wrote:
Do you mean to provide both v6 and v8 from jpeg-turbo? The problem is http://libjpeg-turbo.svn.sourceforge.net/viewvc/libjpeg-turbo/trunk/README-turbo.txt?revision=305&view=markup says the v7/v8 compatibility will not be complete (and since everybody is starting to use libjpeg-turbo I expect it to never be).
Ah, I didn't know that v8 API support will not be 100%. Then I agree to build jpeg6 from libjpeg-turbo sources and jpeg8 from IJG's sources. -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
2010/12/7 Cristian Morales Vega
2010/12/7 Petr Gajdos
: Hi list,
I would like to hear your opinion about future jpeg packaging. I am asked to switch back to jpeg6 in Factory.
Nowadays we have following packages in graphics project: * libjpeg6 (contains only library) * libjpeg7 (contains only library) * jpeg (contains doc files and bin tools) -> libjpeg8 (contains library) -> libjpeg-devel (contains *.h and *.so)
I should do full-fledged jpeg 6 package as jpeg (8) is and we should have it in parallel if I understend correctly (not sure about jpeg 7 package).
jpeg 7 only existed for 6 months, I don't think there is any use for it. But we are already testing this... 11.3 hasn't a libjpeg7 packages, was any bug report created asking for it?
I would appreciate any advice, here is a first thought proposal:
* jpeg6 (contains doc files and bin tools) provides: jpeg, obsoletes: jpeg, conflicts: jpeg8 -> libjpeg6 (contains library) -> libjpeg6-devel (contains development files) provides: jpeg-devel, obsoletes: jpeg-devel, conflicts: jpeg8-devel
* jpeg8 (contains doc files and bin tools) conflicts: jpeg6 -> libjpeg8 (contains library) -> libjpeg8-devel (contains development files) conflicts: jpeg6-devel
Requires should stay same modulo major version.
jpeg6 should be compiled from libjpeg-turbo. But it seems OK to me.
And in case 11.4 finally includes libjpeg-turbo 1.0.1 instead of 1.0.2, please apply http://libjpeg-turbo.svn.sourceforge.net/viewvc/libjpeg-turbo?view=revision&revision=290 to avoid problems when both v6 and v8 libraries are in the same process image. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 12/07/2010 05:10 PM, Petr Gajdos wrote:
Hi list,
I would like to hear your opinion about future jpeg packaging. I am asked to switch back to jpeg6 in Factory.
Nowadays we have following packages in graphics project: * libjpeg6 (contains only library) * libjpeg7 (contains only library) * jpeg (contains doc files and bin tools) -> libjpeg8 (contains library) -> libjpeg-devel (contains *.h and *.so)
I should do full-fledged jpeg 6 package as jpeg (8) is and we should have it in parallel if I understend correctly (not sure about jpeg 7 package).
I would appreciate any advice, here is a first thought proposal:
* jpeg6 (contains doc files and bin tools) provides: jpeg, obsoletes: jpeg, conflicts: jpeg8 -> libjpeg6 (contains library) -> libjpeg6-devel (contains development files) provides: jpeg-devel, obsoletes: jpeg-devel, conflicts: jpeg8-devel
* jpeg8 (contains doc files and bin tools) conflicts: jpeg6 -> libjpeg8 (contains library) -> libjpeg8-devel (contains development files) conflicts: jpeg6-devel
Requires should stay same modulo major version.
Other possibility is to let particular project decide, which jpeg should be default (similarly to libpng12,14 in 11.3). Both libjpeg{6,8}-devel would provide jpeg-devel and conflict with otherproviders(jpeg-devel) and similarly for jpeg{6,8}.
Petr
I see 11.3 graphics blender can't find libjpeg8, what can I change in BuildRequires: libjpeg-devel? Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Dienstag, 14. Dezember 2010 schrieb Dave Plater:
I see 11.3 graphics blender can't find libjpeg8, what can I change in BuildRequires: libjpeg-devel?
Now that's a mean problem. 11.3 repo has a "real" libjpeg-devel, so the provides of libjpeg8-devel aren't looked at. I'm not sure how to fix this problem - but I know changing build requires is wrong ;( Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 12/14/2010 11:59 AM, Stephan Kulow wrote:
Am Dienstag, 14. Dezember 2010 schrieb Dave Plater:
I see 11.3 graphics blender can't find libjpeg8, what can I change in BuildRequires: libjpeg-devel?
Now that's a mean problem. 11.3 repo has a "real" libjpeg-devel, so the provides of libjpeg8-devel aren't looked at.
I'm not sure how to fix this problem - but I know changing build requires is wrong ;(
Greetings, Stephan
I'm asking the blender people which lib to use. Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Dienstag, 14. Dezember 2010 schrieb Stephan Kulow:
Am Dienstag, 14. Dezember 2010 schrieb Dave Plater:
I see 11.3 graphics blender can't find libjpeg8, what can I change in BuildRequires: libjpeg-devel?
Now that's a mean problem. 11.3 repo has a "real" libjpeg-devel, so the provides of libjpeg8-devel aren't looked at.
I'm not sure how to fix this problem - but I know changing build requires is wrong ;(
I disabled and wiped libjpeg8 for 11.3 now and adapted the project config for the other distros. This works for graphics, but you won't get an updated libjpeg8 lib for 11.3 either ;( Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 12/14/2010 12:44 PM, Stephan Kulow wrote:
Am Dienstag, 14. Dezember 2010 schrieb Stephan Kulow:
Am Dienstag, 14. Dezember 2010 schrieb Dave Plater:
I see 11.3 graphics blender can't find libjpeg8, what can I change in BuildRequires: libjpeg-devel?
Now that's a mean problem. 11.3 repo has a "real" libjpeg-devel, so the provides of libjpeg8-devel aren't looked at.
I'm not sure how to fix this problem - but I know changing build requires is wrong ;(
I disabled and wiped libjpeg8 for 11.3 now and adapted the project config for the other distros. This works for graphics, but you won't get an updated libjpeg8 lib for 11.3 either ;(
Greetings, Stephan
I noticed it built again. Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 12/14/2010 12:01 PM, Petr Gajdos wrote:
On Tue, Dec 14, 2010 at 11:40:58AM +0200, Dave Plater wrote:
I see 11.3 graphics blender can't find libjpeg8, what can I change in BuildRequires: libjpeg-devel?
Do you want build against libjpeg-turbo or libjpeg8?
Petr I'll ask the blender devs but I should imagine, from following this and factory threads, that libjpeg-turbo will be the right one. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 12/14/2010 12:01 PM, Petr Gajdos wrote:
On Tue, Dec 14, 2010 at 11:40:58AM +0200, Dave Plater wrote:
I see 11.3 graphics blender can't find libjpeg8, what can I change in BuildRequires: libjpeg-devel?
Do you want build against libjpeg-turbo or libjpeg8?
Petr
The blender people are very interested to see if it works with libjpeg-turbo and because it builds and works fine with libjpeg6, I assume it won't have a problem with libjpeg-turbo. I'm going to put libjpeg-turbo in my home:plater:blender project and give it a try, any known pitfalls? Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 12/14/2010 12:01 PM, Petr Gajdos wrote:
On Tue, Dec 14, 2010 at 11:40:58AM +0200, Dave Plater wrote:
I see 11.3 graphics blender can't find libjpeg8, what can I change in BuildRequires: libjpeg-devel?
Do you want build against libjpeg-turbo or libjpeg8?
Petr
Blender builds with libjpeg-turbo and if it really is a drop in replacement for libjpeg6 it should work. The blender people are thinking of using it as their internal jpeg library and expect a performance increase in jpeg-compressed playback. I'll wait until my latest blender submission is accepted in factory and then put it in graphics with a conditional to change to jpeg8. When is libjpeg-turbo expected in factory? Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (5)
-
Cristian Morales Vega
-
Dave Plater
-
Pavol Rusnak
-
Petr Gajdos
-
Stephan Kulow