Owen DeLong <[EMAIL PROTECTED]> wrote: > I'll agree with that to some extent. However, I should be able to say > "This package is available and it's PREFIX is XYZ" somehow to solve this. > That works with almost every other package I've built using autoconf's > configure.
We welcome patches to the 'configure.in' files. The only issue is that there is a 'configure.in' file in each module directory, so each of those files must be patched. > > The response then, as now, is "don't do that." > > > Yeah... That's nice. Given a choice, I wouldn't. However, I have to work > in an existing environment where I can't dictate policy to the other people > who run this stuff. They're managing a few hundred packages across a few > thousand machines. Since I don't want to try and replace their entire group > with my own opinion of how things should be to build one package, I kind of > need to find an alternative. I understand. What surprises me is that there are *other* networks which manage hundreds of packages across thousands of machines, and they haven't seen the need to screw up the packaging that badly. > > So you have multiple options to get FreeRADIUS working on your > > system, and none involve patches or changes to FreeRADIUS. > > > I didn't figure they would. I offered to provide DIFF's to the INSTALL > document documenting the applicable solution for other users. If you want to change the options to 'configure', then that would be the best way of solving the problem for everyone. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
