Julien BLACHE wrote:
Klaus Darilion wrote:
Regarding radius: When I build radiusclient-ng (using the original
debian build files) the resulting packages are named: libradius-ng
Thus, I wonder why the dependency is named libradiusclient-ng?
Hmm, which version did you use ? I can't find the package on a current
unstable system.
Not on unstable. When I build openser packages, I first fetch
radiusclient-ng from CVS from berlios and build it using the included
debian build files. These packages are named libradius-ng and
libradius-ng-dev.
But when I look at your build dependencies for openser I see:
libradiusclient-ng. Thus I wonder you name the package different. Don't
you use the original build files?
regards
klaus
If there is a reason for naming it libradiusclient-ng, it should be
reported to Maxim to update the source code of radiusclient-ng.
I think it got renamed to allow the old radiusclient and the new one
(standard uneducated guess disclaimer >here<)
Given the radiusclient problem, I'm probably going to add a
debian-sarge packaging directory, baring any objections. Thoughts ?
Adding a packaging directory for sarge will solve the mysql and compat
issue, but not radiusclient naming
I need to dig into that, added on the todo list for tonight.
JB.
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
