[php-maint] Multi version support for php
Walter Kleynscheldt - Hetzner (Pty) Ltd
walter.kleynscheldt at hetzner.co.za
Wed Feb 25 04:49:42 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
On 2015-02-24 06:36 PM, Ondřej Surý wrote:
> perhaps it's because you haven't contributed the side-by-side
packaging you are creating for every version?
Great, if that's the reason then I'm happy and it sounds like there just
hasn't been enough demand for this or the resources to do the work
required for this, rather than a policy or technical reason.
The thing is I don't just want to backported version to be able to
co-exist next to the stable version.
What would be a win for me is if the stable version got the same
treatment as the backported version and didn't provide php5, but
php[stable-version] and got installed in paths/files called
Which in my opinion would make packaging and supporting the multiple
versions much easier.
At the moment we have what we need to support php5.6 on wheezy (we
deviated quite significantly from the php package structure this time
around so can't contribute it unfortunately), so we're happy.
I was really just asking to see if there is a way to make the process
easier for the next release upgrade.
If there is enough excitement and demand for this and if we can work
with you guys for guidance and to assist with the stable package
refactor, then we'd be quite happy to contribute to the maintenance of
the backported version.
> On Tue, Feb 24, 2015, at 11:21, Walter Kleynscheldt - Hetzner (Pty)
>> Can someone provide me with a reason why support for multi versions
of php isn't yet supported on Debian.
>> i.e. I'm running wheezy and I'd like to test the impact of upgrading
all my sites to php5.6.5 by installing it side-by-side to php5.4.4 (from
a backported package).
>> We've been manually creating packages for testing versions of php for
a while now and running it side-by-side the stable release,
>> but having to go through and updating the files in the package
(trying to get around the provides php conflicts etc) and changing paths
to include version numbers and linkages is a bit of a pain to do after
>> What would be really nice, is if php5.4.4 was installed as php544
(with that set as the package name and paths appropriately),
>> because then packages for php5.6.5 could be php565 etc and be
installed to paths containing the version number and binaries or
wrappers symlinked to the selected default version via
update-alternatives (similar to ruby for example)?
>> I'm sure the complexity of the source package and the hassle of
trying to support backports would make this really hard,
>> but at least then it would make it easier for those wanting to create
their own backport packages to do so without jumping through hoops
inside the source package build to satisfy/circumvent dependencies.
>> Some clarity on policy/technical limitations or other would be
>> Kind Regards
>> Walter Kleynscheldt
>> Platform Engineer
>> Hetzner (Pty) Ltd
>> SA Contact Centre:
>> (T) 0861 0861 08
>> | (F) 0861 0861 09
>> (T) +27 21 970 2000
>> | (F) +27 21 970 2001
>> Registration Number: 2005/023926/07
>> Directors: D.M. de Villiers (MD), S.M. Nortjé & H.E. Wencke
>> Web: www.hetzner.co.za <http://www.hetzner.co.za>
>> Disclaimer: www.hetzner.co.za/email-disclaimer
>> pkg-php-maint mailing list
>> pkg-php-maint at lists.alioth.debian.org
<mailto:pkg-php-maint at lists.alioth.debian.org>
>> Email had 1 attachment:
> Ondřej Surý <ondrej at sury.org>
> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pkg-php-maint