On Tue, Apr 05, 2005 at 01:04:16PM +0200, "Jan Henrik Helmuth Lühr" wrote:
> Greetings,
> if you cannot distribute this module in binary, why not doing a source
> distribution, like sl-modem is doing with sl-modem-source?
> For instance:
> If you ship just the sources of this module, every user is free to type
> install-freerad-eap-tls , and build it's own binary.
> Adv:
> - No user has download the source and do it by themself
> - The whole installing-process can be automatic, apart from suggesting the
> user to type a certain command.
> - No legal problems due to actually not shipping any binary.
> - No one has to patch for gnutls.
> Dis-Adv:
> - Depencies of dev-packages
> (Can be removed anyway)
> - Quite a dirty hack.
> (But better than nothing)
> Anyway, I suggest it.
Thankyou for your suggestion. I'll consider it, but it seems unlikely to
me to happen for the following reasons:
- building modules outside of the build process is completely untested
by me. I'm not even sure _how_ to do it, given we don't distribute
the bits needed to do so. (Header files et. al.) Once libradius has a
package of its own, and a -dev package to go with it, this will be
easier to organise.
- I'm hoping someone will give in, and contribute a gnuTLS patch. The
1.1.0 release will have a rearchitectured EAP module set, which means
only one place to convert from OpenSSL to gnuTLS.
- I'm trying to not futz with things too much due to the upcoming Sarge
release. I'd rather a missing feature than a broken feature being
locked into Sarge for years.
- The script would have to either produce its own package, or somehow
install into /usr/local/ somewhere. The former is more work, and the
latter is rather unappealing.
--
Paul "TBBle" Hampson, <email address hidden>
7th year CompSci/Asian Studies student, ANU
Shorter .sig for a more eco-friendly paperless office.
On Tue, Apr 05, 2005 at 01:04:16PM +0200, "Jan Henrik Helmuth Lühr" wrote:
> Greetings,
> if you cannot distribute this module in binary, why not doing a source
> distribution, like sl-modem is doing with sl-modem-source?
> For instance: freerad- eap-tls , and build it's own binary.
> If you ship just the sources of this module, every user is free to type
> install-
> Adv:
> - No user has download the source and do it by themself
> - The whole installing-process can be automatic, apart from suggesting the
> user to type a certain command.
> - No legal problems due to actually not shipping any binary.
> - No one has to patch for gnutls.
> Dis-Adv:
> - Depencies of dev-packages
> (Can be removed anyway)
> - Quite a dirty hack.
> (But better than nothing)
> Anyway, I suggest it.
Thankyou for your suggestion. I'll consider it, but it seems unlikely to
me to happen for the following reasons:
- building modules outside of the build process is completely untested
by me. I'm not even sure _how_ to do it, given we don't distribute
the bits needed to do so. (Header files et. al.) Once libradius has a
package of its own, and a -dev package to go with it, this will be
easier to organise.
- I'm hoping someone will give in, and contribute a gnuTLS patch. The
1.1.0 release will have a rearchitectured EAP module set, which means
only one place to convert from OpenSSL to gnuTLS.
- I'm trying to not futz with things too much due to the upcoming Sarge
release. I'd rather a missing feature than a broken feature being
locked into Sarge for years.
- The script would have to either produce its own package, or somehow
install into /usr/local/ somewhere. The former is more work, and the
latter is rather unappealing.
--
Paul "TBBle" Hampson, <email address hidden>
7th year CompSci/Asian Studies student, ANU
Shorter .sig for a more eco-friendly paperless office.