[Cooker] what to do with phpldapadmin?

[Glen Ogilvie]

Hi,

I am being the maintainer for the phpldapadmin package.

I have a problem with it, and am not sure what is best, so am asking for some
advise. The current version of phpldapadmin does not work with php 5.3,
because some of the functions it uses have been deprecated, which now produce
warnings, and some of the functions it calls have been changed.

The new version of phpldapdamin from source forge (1.2.0.4) appears to have
some fairly major bugs and unimplemented features in it, making it not ideal.

I've logged a bug or two with the project, but am wondering from a Mandriva
perspective, what is best to do with it.  I've been trying to patch the old
version to work with the new php 5.3, but this seems to be a bigger job than
just a few tweaks.

Advise is appreciated.

Regards
Glen Ogilvie

put the new version in /backports so people can choose but not be
automatically upgraded, maybe even put the new version in the package
name

[Glen Ogilvie]

On Wed, 04 Nov 2009, aapgorilla wrote:
> put the new version in /backports so people can choose but not be
> automatically upgraded, maybe even put the new version in the package
> name

Is the a lot of point releasing a buggy version into backports?  I am thinking
the new version should not be packaged until it at least mostly works.  

Glen

[Colin Guthrie-8]

'Twas brillig, and Glen Ogilvie at 04/11/09 08:22 did gyre and gimble:
> On Wed, 04 Nov 2009, aapgorilla wrote:
>> put the new version in /backports so people can choose but not be
>> automatically upgraded, maybe even put the new version in the package
>> name
>
> Is the a lot of point releasing a buggy version into backports?  I am thinking
> the new version should not be packaged until it at least mostly works.  

Hmm, I use this at work. I can't use PHP 5.3 on my development machines
due to http://bugs.php.net/bug.php?id=50027 and will be using PHP 5.2.11
for a good while longer even after upgrading (mostly) to 2010.0.

But that said, the machine that runs phpldapadmin is not a development
nor public facing machine so was intending to use PHP 5.3 there.

So without knowing how much work is involved, I'd imagine the
deprecated, but still implemented, calls can be fixed with a simple @
prefix and the changes can be bashed through. So if you like I'll do
that patching, but it wont be for a couple weeks.

Col

--

Colin Guthrie
cguthrie(at)mandriva.org
http://colin.guthr.ie/

Day Job:
   Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
   Mandriva Linux Contributor [http://www.mandriva.com/]
   PulseAudio Hacker [http://www.pulseaudio.org/]
   Trac Hacker [http://trac.edgewall.org/]

[Glen Ogilvie]

On Wed, 04 Nov 2009, Colin Guthrie wrote:

> 'Twas brillig, and Glen Ogilvie at 04/11/09 08:22 did gyre and gimble:
> > On Wed, 04 Nov 2009, aapgorilla wrote:
> >> put the new version in /backports so people can choose but not be
> >> automatically upgraded, maybe even put the new version in the package
> >> name
> >
> > Is the a lot of point releasing a buggy version into backports?  I am
> > thinking the new version should not be packaged until it at least mostly
> > works.
>
> Hmm, I use this at work. I can't use PHP 5.3 on my development machines
> due to http://bugs.php.net/bug.php?id=50027 and will be using PHP 5.2.11
> for a good while longer even after upgrading (mostly) to 2010.0.

That bug looks like a bit of a tricky one to solve.. nasty.

> But that said, the machine that runs phpldapadmin is not a development
> nor public facing machine so was intending to use PHP 5.3 there.
>
> So without knowing how much work is involved, I'd imagine the
> deprecated, but still implemented, calls can be fixed with a simple @
> prefix and the changes can be bashed through. So if you like I'll do
> that patching, but it wont be for a couple weeks.

I am part way with the patching, so it would be great if you are keen to work
on it with me.  No point you writing the same patches I have already got
working.  I just discovered once I started, it's got a few places that need
attention by the looks of it, so the number of bit needing patching is a few,
partly because of the way that phpldapadmin catches errors.

I'll email you the patches I have directly, in a day or two when I've got them
to a slightly less broken state.

Regards
Glen Ogilvie