Bug 864548

Summary:	Split out iv?
Product:	[Fedora] Fedora	Reporter:	katastrophal
Component:	OpenImageIO	Assignee:	Richard Shaw <hobbes1069>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	18	CC:	hobbes1069
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-02 04:16:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description katastrophal 2012-10-09 14:47:37 UTC

Would it be possible to split iv out of this package (maybe in a seperate package)? iv is the only binary here that requires qt, all other binaries build just fine without. If you could split it out, you could drop this dependency. iv is considered an optional component by OpenImageIO itself, as pointed out on their Build instruction page [1]. This would ultimately shorten the dependency chain of blender.

[1] https://sites.google.com/site/openimageio/checking-out-and-building-openimageio

Comment 1 Richard Shaw 2012-10-09 16:18:27 UTC

Yeah I've been thinking about it but there were not too many direct users of OIIO but perhaps that's changing. I just did a 1.0.9 build... I should have done it then, oh well. 

I'll get to it when I get a chance. Do you have any preference on the sub-package name?

Comment 2 katastrophal 2012-10-09 18:23:21 UTC

Awesome :-)

I have no real preference for a package name. iv, or OIIO-iv or something along the line is probably the best choice? I don't know much about fedora package naming conventions though.

Comment 3 Richard Shaw 2012-12-10 21:47:22 UTC

Hopefully will have time to fix this soon...

Comment 4 Richard Shaw 2013-01-14 13:59:34 UTC

Ok, I'm finally getting to this :) I've been tied up with mythtv and avidemux over on RPM Fusion. I might as well update to the latest version so I'll have to do some abi compatibility testing first.

Comment 5 Fedora Update System 2013-01-17 19:04:06 UTC

OpenImageIO-1.0.11-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/OpenImageIO-1.0.11-1.fc17

Comment 6 Fedora Update System 2013-01-17 19:04:23 UTC

OpenImageIO-1.0.11-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/OpenImageIO-1.0.11-1.fc16

Comment 7 Fedora Update System 2013-01-17 19:04:35 UTC

OpenImageIO-1.0.11-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/OpenImageIO-1.0.11-1.fc18

Comment 8 Fedora Update System 2013-01-20 03:09:08 UTC

Package OpenImageIO-1.0.11-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing OpenImageIO-1.0.11-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-1047/OpenImageIO-1.0.11-1.fc17
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2013-02-02 04:16:25 UTC

OpenImageIO-1.0.11-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2013-02-02 04:30:40 UTC

OpenImageIO-1.0.11-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2013-02-02 04:33:15 UTC

OpenImageIO-1.0.11-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.