> 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? >
Yes. >> 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. I could ... I guess I should also get comments on my ldap article from them too before I publish. The issue though, is that we can't put it in as a new schema file, if we want people to be able to upgrade, keeping their configs and data, without editing files manually while their authentication database is down and users are complaining ... So, it really should stay in the schema file it was in, so no matter which schema files the admin commented/uncommented, he won't see a change ... > >> 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. > Note I am talking about putting packages into cooker and Club. So, for example, I updated kdirstat to 2.3.7-1mdk in cooker, but 2.3.7-0.9mdk in Club. Since we're bumping the version number anyway, it's guaranteed to update whatever was in 9.1 ... With samba, you will never see a -1mdk in cooker though (1.Xmdk reserved for builds from official source). >> 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... No, all SRPMs will be available, I just don't like paying too much for people downloading RPMs from my site (which reminds me, I should move grass-5.0.2 for 9.1 onto Club ... and maybe 5.0.0 for 8.2 also which together accounted for 2.5GB last month @$0.10/MB cost to us when we shortly start paying for all our bandwidth). Buchan
