[php-maint] fixed php4/php5 packages uploaded

[Steve Langasek]

On Sat, Nov 18, 2006 at 02:24:22PM +0100, sean finney wrote:

> 4) bump the "upstream version" and ship a new orig.tar.gz with both
> trees in seperate directories, and build accordingly.
> 5) if the difference isn't too huge between the two, create the second
> build directory via a patch against the first
> 6) compile the modules into the php engines themselves (which would
> affect dependencies)

If the PECL versions of these modules are no longer compatible with php4,
for my part I have no particular objection to re-merging them into the main
tree.  In terms of transitions, any solution that gets the binary versions
of packages *matching* the source versions they're built from is a good one.

I don't think 6 is a good choice.  *None* of these split-off extensions are
without other lib dependencies.

In contrast, I'm greatly puzzled to learn that the pdo extension has been
built as a DSO and placed in the php5-common package.  If it's so "common"
that it doesn't get its own extension package, why isn't *this* extension
being built into the engines?

> as i've said before, i think that (3) is the best option on my book
> for the modules that were previously split off the main tree.  if that's
> impossible w/out going through NEW, it might be worth looking at (5) as
> an alternative.  (6) is also worth a look if the dependency addition
> is zero or minimal.

I agree, but only in light of the news that the off-tree versions of the
modules aren't backwards-compatible with php4.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon at debian.org                                   http://www.debian.org/