On Sat, Feb 12, 2011 at 11:17:20AM +0100, Remi Collet wrote:
Hi,
I plan to work on PHP spec file for Arch Specific Requires
(the %{?_isa} macro use)
Great, thanks!
Some changes are quite trivial
Requires: php-common%{?_isa} = %{version}-%{release}
But we have a lot of virtual provides which need to be fixed
Provides: php-bz2%{?_isa}, php-calendar%{?_isa}, php-ctype%{?_isa}...
(keeping the non-arch specific ones for noarch package)
Sounds good. Is this backwards-compatible, such that any package which
Requires: php-bz2
will still work a php package using the arch-specific provides? It's
not obvious from the guideline drafts.
Shouldn't we also use version in this ?
Provides: php-bz2%{?_isa} = %{version}-%{release}
This came up before. We can... but some (though possibly a minority) of
the bundled extensions do encode an "extension version" which is
*different* to the PHP version.
$ php --re spl | head -1
Extension [ <persistent> extension #22 SPL version 0.2 ] {
so should we use %{version} for spl or 0.2?
If we also change
Provides: php(api)%{?_isa} = %{apiver}
Provides: php(zend-abi)%{?_isa} = %{zendver}
This will requires a Guidelines change for pecl package to use
Requires: php(zend-abi)%{?_isa} = %{php_zend_api}
Requires: php(api)%{?_isa} = %{php_core_api}
@Joe, do you plan to change httpd ? to be able to
Requires: httpd-mmn%{?_isa} = %{httpd_mmn}
I don't get from the drar
In which branch should we do this change ?
master + f15?
Regards, Joe