On Fri, 30 May 2003 20:24:12 +0200, bgmiln wrote:
>
> 
> BTW, I will investigate the auxiliary objectclass account

Are you referring to the message Luke Howard sent to OpenIT's Core-Dev
list that I referred to in the other openldap 2.1 thread?

> which is in
> pam_ldap, and see what can be done about getting in into openldap

Yes, this would be nice.

> (I would
> guess it should go back into the schema file it was in for 2.0.x).

You might just want to e-mail Luke/Core-Dev and copy the openldap list and
see what the agreement is on getting it into openldap.  It might just wind
up being yet another schema patch in the Mandrake RPM.

> In terms of release numbers etc, I normally decrement (ie 1mdk->0.9mdk as
> I did with kdirstat) the release when it goes into Club,

But then how does one get the update if they are running 1mdk (to use your
example)?  Urpmi will see that what's in Club is lower in version number
and not do an update when in reality one might want to update.

What I do here locally, is to use decimal increments > last Mandrake
released and < what will be their next release.  Again to continue
your example, if they release (say into 9.1) foo-1.0-1mdk, if I want to
update that, I make mine foo-1.0-1.1mdk, and then their next release will
be foo-1.0-2mdk.  Urpmi is happy to update all of these in the right
order.

> so that we are
> guaranteed the next release will update the Club package (even if the
> cooker package is never updated again).

BTW, just so you know and that it's written somewhere, I had to rebuild
postfix (changing references to the sasl v1 lib to v2 and adding a
-I/usr/include/sasl in the spec file) in order to get SMTP AUTH working
with TLS and your OpenLDAP 2.1 RPMs.

But again, I have to plead that all of this stuff be made available
outside of Club (in addition to Club, if appropriate) as I (and I am sure
others) simply cannot afford to be a Club member when it has to come out
of savings just like the rent, heating and Internet bills.  When I get an
income, things will be different, but until then...

b.



Reply via email to