[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freeradius-users
Subject:    Re: Problem: Can't compile rlm_ldap if OpenLDAP isn't in /usr/local/lib and /usr/lib/include
From:       aland () striker ! ottawa ! on ! ca
Date:       2001-07-28 17:16:45
[Download RAW message or body]

<jan@tomasek.cz> wrote:
> thanks for quick reply. But I realy don't understand why are you attacking
> me?! Maybe is that feeling caused by my poor english but ... NO I don't
> want start an fight ... no one is interested in reading that stuf.

  I agree.

> Lots of well known software like Apache, OpenLDAP, PHP ... allows me
> specify path where some kind of libs are installed, so why not FreeRadius?

  I agree.  FreeRADIUS *should* do that.  I'm looking at adding that
now.

> I understand you provide this for free, you don't want to support stupid
> users ... no problem. I wasnt saing that you are doing something wrong.

  It's not the "stupid" users that frustrate me.  It's the people who
expect something for free, and who get upset when the free software
doesn't do exactly what they want, when they don't even know what they
want.
 
> I told that I don't need help, I just want to inform you that someone
> other might have similar problems with configure scripts you wrote.

  Your previous message was the first time I saw that kind of
problem.  Your concern was that it didn't work, and I didn't see much
in the way of suggestions as to how to fix the problem.


  As I said in my previous message, I'm currently adding in the
ability to specify module library and include directories.  This
should be in the upcoming 3.2 release.


  And as a further explanation, I've seen a number of messages
(including private ones to me) from people who misconfigured their
system, and then expected FreeRADIUS to magically figure out what to
do.  So I'm *very* biased against unusual systems, and I try to be
honest (if a little blunt) in making that bias clear.

  Alan DeKok.


[prev in list] [next in list] [prev in thread] [next in thread]