Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Jul 2003 11:55:21 +0200 (CEST)
From:      Christian Kratzer <ck@cksoft.de>
To:        Oliver Eikemeier <eikemeier@fillmore-labs.com>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: ports/54202: [MAINTAINER PATCH] unify port net/openldap20 with net/openldap22
Message-ID:  <20030710114206.M84774@majakka.cksoft.de>
In-Reply-To: <3F0A09E7.9080502@fillmore-labs.com>
References:  <3F0A09E7.9080502@fillmore-labs.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

a couple of comments ...

On Tue, 8 Jul 2003, Oliver Eikemeier wrote:
> - unify port net/openldap20 with net/openldap22 (easier to maintain)

you seem to be very active with the openldap ports currently and I would
suggest that you take over the openldap21 port from me for consistency
purposes.  Feel free to update yourself as the maintainer if you like.

> - install additional documentation
> - don't install .la files
> - make start/stop scripts compatible with net/openldap22
> - better package building
> - improved installation messages
> - package name is openldap again - should have never been renamed

it happened when my openldap21 port was committed in February this year.
I had submitted the port with packagename openldap and version 2.1.x but
there was some discussion with the committers that policy was changing and
the new scheme was now preferred.

Of course I would prefer changing back but this will break dependent ports
once again.  If we change back I would very much like this to stay and not
be changed back again. Perhaps this should be documented in the Makefiles.

I would think that the maintainers of dependent ports would not bee too happy
to change the openldap dependencies every couple of months.

> - bump portrevision
>
> Differences between net/openldap20 and net/openldap22:

openldap22 is still alpha and openldap21 is the currently preferred
version. openldap20 although still in use is EOL and should be depreciated.

Even if openldap22 could currently be ok we should not induce openldap
newbies to go with the lastest and greatest alpha code that could break
any time.  Remeber the problems with the berkeley db backend and with
threads in early openldap2.1 releases.  Thinks can break from one day
to another and rebuilding all your dependencies to go back can be quite
stressing ...

Greetings
Christian

-- 
CK Software GmbH
Christian Kratzer,         Schwarzwaldstr. 31, 71131 Jettingen
Email: ck@cksoft.de
Phone: +49 7452 889-135    Open Software Solutions, Network Security
Fax:   +49 7452 889-136    FreeBSD spoken here!



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030710114206.M84774>