Le 12/02/2011 17:05, Joe Orton a écrit :
> 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.
Yes.. not obvious.
For "real" package, RPM generate 2 provides, for example
php-mysql
php-mysql(x86-64)
So, for virtual, i think we need to do the same
php-mysqli
php-mysqli(x86-64)
which is my plan.
> @Joe, do you plan to change httpd ? to be able to
> Requires: httpd-mmn%{?_isa} = %{httpd_mmn}
I don't get from the drar
Sorry... I don't understand your answer..
I think this is really not clear, and this should be raised on the
packaging ML.
I have notice than xulrunner already provides the 2
Provides: gecko-libs = %{gecko_verrel}
Provides: gecko-libs%{?_isa} = %{gecko_verrel}
but this is probably a terrible issue for php, httpd, ... as we will
have to maintain distinct spec file in each branch for each extension
(pecl ones)....
Remi.