[opensuse-packaging] apache2-mod_authnz_external depending on Apache version
Hi, this is probably answered before, but I didn't find anything in the archives and Packaging Guidelines. apache2-mod_authnz_external comes upstream in different versions for different apache versions: 3.3.x is for Apache 2.3/2.4 3.2.x is for Apache 2.2 Currently in https://build.opensuse.org/project/show/Apache:Modules we have version 3.2.6, working and compiling only for apache 2.2. So it does not build for newer distros, i.e. openSUSE 13.1 and newer. I branched and updated my branch to 3.3.2. It builds for the openSUSE 13.1 and newer and for most Apache_* targets. What is the best way to bring 3.2.6 for older distros and 3.3.2 for newer distros to the Repositories? I thought about including version number in the package name. That would probably mean to also change name of the existing package? Is there is a way to build different versions depending on either distribution/repository or even better depending on apache version? TIA. -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Wednesday 2014-01-29 09:53, vetter@physik.uni-wuerzburg.de wrote:
this is probably answered before, but I didn't find anything in the archives and Packaging Guidelines. apache2-mod_authnz_external comes upstream in different versions for different apache versions: 3.3.x is for Apache 2.3/2.4 3.2.x is for Apache 2.2
Typically, there would have to be two packages that conflict with each other: apache2-mod_authnz_external (for 3.3), requiring apache2-mpm >= 2.4 and nothing else and apache2-mod_authnz_external-3_2 (for 3.2), requiring apache2-mpm < 2.4 and conflicting with apache2-mod_authnz_external. This is (very loosely) indicated by http://en.opensuse.org/openSUSE:Package_naming_guidelines#Multiple_packages_...
I thought about including version number in the package name. That would probably mean to also change name of the existing package?
Indeed it would. (And it's just a copy of the existing package before you SR the new version.) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
PMing maintainers, too Jan Engelhardt <jengelh@inai.de> wrote on 30/01/2014 17:21:11:
On Wednesday 2014-01-29 09:53, vetter@physik.uni-wuerzburg.de wrote:
this is probably answered before, but I didn't find anything in the archives and Packaging Guidelines. apache2-mod_authnz_external comes upstream in different versions for different apache versions: 3.3.x is for Apache 2.3/2.4 3.2.x is for Apache 2.2
Typically, there would have to be two packages that conflict with each other: apache2-mod_authnz_external (for 3.3), requiring apache2-mpm >= 2.4 and nothing else
Is there a reason why you use "apache2-mpm >= 2.4" instead of "apache2 >= 2.4"
and
apache2-mod_authnz_external-3_2 (for 3.2), requiring apache2-mpm < 2.4 and conflicting with apache2-mod_authnz_external.
Do we really need the conflict when we have the requirement on apache version? There will only be built either the old or the new module (meaning XOR).
This is (very loosely) indicated by http://en.opensuse.org/
openSUSE:Package_naming_guidelines#Multiple_packages_for_the_same_software
I thought about including version number in the package name. That
would
probably mean to also change name of the existing package?
Indeed it would. (And it's just a copy of the existing package before you SR the new version.)
I prepared both versions in OBS: 3.2.6 for apache 2.2: https://build.opensuse.org/package/show/home:asvetter:branches:Apache:Module... 3.3.2 for apache 2.4: https://build.opensuse.org/package/show/home:asvetter/apache2-mod_authnz_ext... Are maintainers ok with that? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tuesday 2014-02-04 09:55, vetter@physik.uni-wuerzburg.de wrote:
Typically, there would have to be two packages that conflict with each other: apache2-mod_authnz_external (for 3.3), requiring apache2-mpm >= 2.4 and nothing else
Is there a reason why you use "apache2-mpm >= 2.4" instead of "apache2 >= 2.4"
No reason; I now see that apache2-MPM is also unversioned so it wouldn't work. "apache2 >= 2.4" it is.
apache2-mod_authnz_external-3_2 (for 3.2), requiring apache2-mpm < 2.4 and conflicting with apache2-mod_authnz_external.
Do we really need the conflict when we have the requirement on apache version?
Probably not.
I prepared both versions in OBS: 3.2.6 for apache 2.2: https://build.opensuse.org/package/show/home:asvetter:branches:Apache:Module...
3.3.2 for apache 2.4: https://build.opensuse.org/package/show/home:asvetter/apache2-mod_authnz_ext...
Are maintainers ok with that?
Posting an SR is the way to "ask" :) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (2)
-
Jan Engelhardt -
vetter＠physik.uni-wuerzburg.de