https://bugzilla.rpmfusion.org/show_bug.cgi?id=2054
Bug #: 2054
Summary: Review request: OCE - OpenCASCADE Community Edition
Classification: Unclassified
Product: Package Reviews
Version: Current
Platform: All
OS/Version: GNU/Linux
Status: NEW
Severity: normal
Priority: P5
Component: Review Request
AssignedTo: rpmfusion-package-review(a)rpmfusion.org
ReportedBy: hobbes1069(a)gmail.com
CC: rpmfusion-package-review(a)rpmfusion.org
Created attachment 760
--> https://bugzilla.rpmfusion.org/attachment.cgi?id=760
Rpmlint output of installed library.
SPEC: http://dl.dropbox.com/u/34775202/OCE/OCE.spec
SRPM: http://dl.dropbox.com/u/34775202/OCE/OCE-0.7.0-1.fc15.src.rpm
Description:
OpenCASCADE Community Edition (OCE) is a suite for 3D surface and solid
modeling, visualization, data exchange and rapid application development. It
is an excellent platform for development of numerical simulation software
including CAD/CAM/CAE, AEC and GIS, as well as PDM applications.
rpmlint output from SRPM:
$ rpmlint mockbuild/15/OCE/OCE-0.7.0-1.fc15.src.rpm
OCE.src: W: invalid-license Open CASCADE Technology Public License
OCE.src: W: invalid-url Source0: tpaviot-oce-OCE-0.7.0-0-ga384024.tar.gz
1 packages and 0 specfiles checked; 0 errors, 2 warnings.
rpmlint doesn't know about this specific license. The source URL is in the
comments because it's a github release.
This is not permitted in Fedora because the license is considered non-free[1]
and if approved will need to go into the non-free repository.
[1]
https://fedoraproject.org/wiki/Licensing/Open_CASCADE_Technology_Public_L...
--
Configure bugmail: https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.

Hi,
the current xine-lib maintainer speaking. :-)
The Xine project:
http://www.xine-project.org/home
has recently released a new major version, version 1.2.0.
Unfortunately, among the list of changes:
http://sourceforge.net/projects/xine/files/xine-lib/1.2.0/README.txt.asc/...
there are these new "features":
* Use libavutil-provided implementations for CRC, SHA1 and BASE64 algorithms,
this makes use of libavutil even outside the FFmpeg decoding plugin,
but avoid duplication of algorithms between different plugins.
* Use av_mallocz() when xine_xmalloc_aligned() wouldn't be needed.
* FFmpeg is now required as an external dependency; if you want to build
xine-lib from source, please download a copy of FFmpeg from their SVN
server.
which basically mean that xine-lib now has a global, non-optional dependency
on FFmpeg's libavutil library.
So there are 4 possible ways forward:
(a) Stick with 1.1.x forever. I don't think that's a good idea in the long
run, upstream won't be providing security fixes for the old branch forever.
(b) Package libavutil (and only libavutil) from FFmpeg in Fedora. (I don't
think libavutil, as opposed to libavcodec, is actually patent-encumbered,
though that'd also have to be checked.) The issue there is that FFmpeg
upstream obviously doesn't support this. It would need some more black
packaging magic of the kind already done in xine-lib, and more legal
auditing. I don't think I want to investigate going down that road.
(c) Bundle parts or all of libavutil with xine-lib. Yuck!!!
(d) Move the whole thing (back) to RPM Fusion (where it originally was, before
we started needing xine-lib for Amarok and Phonon, which both no longer
use it). It would go to the Free section, of course.
My proposal is to go with (d).
The following packages currently depend on xine-lib:
* gxine
* (k9copy – already in RPM Fusion, not affected)
* kaffeine (my package, the reason why I maintain xine-lib in the first place)
* oxine
* xine-plugin
* xine-ui
These packages would have to move to RPM Fusion along with xine-lib.
In Kaffeine's case, upstream is switching from xine-lib to MPlayer in their git
repository, so it will likely have to move to RPM Fusion sooner or later
anyway. This means the affected packages are basically *xine*.
So my plan is to retire (for my packages, resp. have the respective maintainer
retire) the listed packages in Fedora for Fedora ≥ 17 and get (or have the
respective maintainer get) them into RPM Fusion Free instead. (I'd take care
of xine-lib and kaffeine myself, I hope the maintainers of the other packages
will take care of them.)
Comments? Objections?
Kevin Kofler

Hi,
As you may know, the libaacs package from RPM Fusion rely on openssl
functions that have been disabled in the fedora package for some
reason.
This lead the libaacs package to be partially unuseable for it's target usage.
I would like to list what would be possible workarounds for this
issue. We likely need to build a openssl-freeworld package:
- Build a similar package and drop a file in ld.conf.d to make it
system wide ? (the freetype-freeworld way)
This seems unpractical as we may produce unknown behavior and
un-certified code path with others applications.
- Build a shared object with another SONAME so packages liked with the
freeworld version will not conflict with package linked with the
fedora version.
(It will eventually be possible to relink the so to the the fedora
SONAME manually in a second step).
- Build the freeworld version statically.
The question to sync the patch between fedora and RPM Fusion VCS is a
big question until we move to git, so I hope that progress will be
made in this area soon.
If not we may experiment an openssl-freeworld to be possibily behind
the fedora version.
Any thoughts on that ?
Nicolas (kwizart).