OK, I feel bad about this as half of it is my fault, but after I looked harder at the packaging guidelines in re bundling today, I think it's fair to say owncloud is clearly violating the hell out of them.
I and before me Gregor had been proceeding, I think, on the belief that unpackaged things could be bundled, but that really doesn't seem to be the case:
https://fedoraproject.org/wiki/Packaging:Treatment_Of_Bundled_Libraries , "bundled libraries being defined as libraries which exist and are mantained independently, whether or not they are packaged separately for Fedora" and https://fedoraproject.org/wiki/Packaging:Guidelines#Duplication_of_system_libraries , "In this RPM packaging context, the definition of the term 'library' includes: compiled third party source code resulting in shared or static linkable files, interpreted third party source code such as Python, PHP and others."
It really wasn't compliant all the way back to review, in my opinion. The originally imported spec:
has a 'bundling notes' section:
# bundling notes:
## smb4php - forked php class from http://www.phpclasses.org/package/4129-PHP-Stream-wrapper-to-access-Windows-shared-files.html
## openid/phpMyID - forked from http://siege.org/projects/phpMyID and adjusted to oC needs
## openid/SimpleOpenID - adjusted class from http://roosenmaallen.com/2008/03/20/simpleopenid-for-php/
## Google - copy of a google playground project https://code.google.com/p/gdata-samples/source/browse/trunk/oauth_playground/
# containing random OAuth.php lib from http://oauth.googlecode.com/svn/code/php/ - I don't know what to say
## mediawiki contains two files picked from the mediawiki distribution
# Fedora packages mediawiki but not in a way that it's files would be reusable
# (i.e. the package doesn't contain the files itself but the tarball + deployment
you could argue that some or all of those might have been worth an FPC exception, but according to the policy they clearly *needed* an FPC exception, not just packager and reviewer judgement calls, which seems to have been what was used.
Since then, well, the details have changed, but things have overall gotten worse. Here are the current 'bundling notes' for 8.0.7:
## 3rdparty/patchwork - https://github.com/nicolas-grekas/Patchwork-UTF8
# "patchwork/utf8": "~1.1"
# Used to set a UTF-8 locale (function isSetLocaleWorking does not
# just test whether setlocale works, it actually asks Patchwork to
# set a locale) and for its pure PHP implementation of the Normalizer
# class otherwise found in php-intl. See lib/private/util.php
# Patch from adamw to use php-intl's if available:
# We'd also have to set a UTF-8 locale some other way to entirely
# replace OC's use of Patchwork.
## 3rdparty/mcnetic/phpzipstreamer - https://github.com/McNetic/PHPZipStreamer
# "mcnetic/phpzipstreamer": "dev-master"
# OC's copy is somewhat behind upstream, and slightly forked: they imported
# it on 2014-02-20, and added a downstream patch to make it work with
# PHP 5.3 on 2014-03-17:
# Upstream implemented a different fix against PHP 5.3 on 2014-03-14:
# but OC has never synced with that fix. See:
## apps/files_external/3rdparty/smb4php - forked php class from
# Replaced by https://github.com/icewind1991/SMB post-8.0
## 3rdparty/punic - https://github.com/punic/punic
# "punic/punic": "1.1.0"
# Used in date localization: lib/private/l10n.php
# Should be straightforward to unbundle
If someone wants to take the trouble to make OC compliant, I'd suggest they need to package and unbundle punic and patchwork, and probably request an exception for the phpzipstreamer fork (that whole situation is kind of a mess) and the smb4php fork.
8.1 gets rid of the smb4php fork (though the replacements need to be packaged - I believe Remi is on that), but adds a major wrinkle in that OC now needs sabredav 2.1, but we also have Horde depending on sabredav, and that still needs 1.8. So we'd need to split that package up somehow. This has already been discussed between me and Remi and Shawn to some extent. There are various other new unpackaged deps in 8.1 too.
I just submitted review requests for php-punic (bug #1262468) and php-patchwork-utf8 (bug #1262469)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
As a quick update to this...
The 8.2.2 work has brought the bundling down to:
why pear/console_getopt and pear/pear-core-minimal, both are available ?
Because I managed to miss them whilst working through the others....
Guess there will be a 8.2.2-2 in due course with more hacking to unbundle done on it ;)
mcnetic/phpzipstreamer => review #1296901
deepdiver1975/tarstreamer => owncould/tarstreamer => review #1296939
As I recall, the phpzipstreamer in ownCloud is forked from upstream's, there are more detailed notes in the spec file; so just packaging upstream may not be enough to unbundle OC's usage.
@Admn, thanks for the notice, but I think this is ok now.
From 8.2.2 3rdparty/composer.lock
Which is the exact revision in https://github.com/remicollet/remirepo/blob/94ad2fa705b18be2d1fd223c6b9a44289f0ab032/php/php-mcnetic-zipstreamer/php-mcnetic-zipstreamer.spec#L9
Diffing the sources is also ok (the only diff is my patch to fix the test suite)
ah, cool, I guess they finally reconciled with upstream then.
league/flysystem => review request #1298475
interfasys/lognormalizer => review #1298649
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
So the 8.2 which is in progress of going out will be completely unbundled of php libraries thanks to Remi's hard work.
The expectation is that 9.0 will be the same.
Perhaps just test unbundling jquery to js-jquery1 ?
Well thanks to the sterling work of many there are no bundled PHP libraries in owncloud in our repos at this point.
1) EPEL6 - about to be retired so can be ignored
2) EPEL7 - the 8.2.3 update which strips all the php bundling and the autoloader about to hit testing
3) F22/23/24/rawhide - the initial 8.2.3 update has already gone out with the unbundling, in testing is an additional bundling we caught in testing and the autoloader based build
As a result of the above I'm going to close this with NEXTRELEASE finishing the clean up.