On Mon, Jan 30, 2006 at 12:00:25PM -0500, Alan DeKok wrote:
Nicolas Baradakis <nbk@sitadelle.com> wrote:
I don't know if it's too soon to plan a release date for 1.1.1, as 1.1.0 has some annoying known problems:
We can put out 1.1.1 as soon as we have fixes for 1.1.0.
- an error on x86_64 machines when reading dictionnaries. - compilation fails on FreeBSD because of rlm_otp. - rlm_eap_peap and rlm_eap_ttls have libtool problems on Debian.
Those 3 alone should result in a 1.1.0.
If we get 2 quickly and the third isn't already visible, I'd vote vote for a quick 1.1.1 release. Especially the AMD64 problem, since the other two are module-related rather than core-releated.
- pull eap fixes from CVS head to address Debian's issues. I found many changes not in branch 1.1 but I've no idea whether they are safe or not: - moved TLS code from rlm_eap_tls to libeap.
Yes.
And a reminder, that alone won't fix the Debian concern. Someone has to port libeap to gnuTLS... I think I once volunteered myself for that, so I should get cracking on it. Then once the libeap-centralised-SSL changes get into the 1.1 branch, I'll be ready. ^_^
- maybe undelete the database schema for MSSQL server? We could put the file under src/modules/rlm_sql/drivers/rlm_sql_unixodbc for example.
Put the schemas under /doc, or create a /doc/examples and put them there.
For reference, the Debian build already hunts down the schemas and puts them in /usr/share/doc/freeradius/examples, as well as the various scripts and the rlm_perl example script. -- ----------------------------------------------------------- Paul "TBBle" Hampson, Bsc, MCSE On-hiatus Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) Paul.Hampson@Pobox.Com Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. -- Kristian Wilson, Nintendo, Inc, 1989 License: http://creativecommons.org/licenses/by/2.1/au/ -----------------------------------------------------------