On Tue, Apr 01, 2008 at 01:23:11AM +0100, Stephen Gran wrote:
> > Ugh. This would usually go into a libradius-1.1.7 package, but because
> > this is a just a shared object file (rather than a proper shared library),
> > you can put it into something like freeradius-common, and keep a strict
> > dependency on it.
>
> I was thinking of an arch all -common, an arch any -utils, a library
> package, and a server package. But yes, the dependencies need to be
> strict.
Right, if you have a relatively large arch-indep file percentage... putting
the documentation in there will probably tip the scale to make it worth the
while, but I didn't check.
> > Also, radclient needs the dictionary files, so /etc/freeradius/dictionary
> > and /usr/share/freeradius/dictionary* should go in the common package too.
>
> This is being worked on for the 2.x packages now. Amusingly, for built
> libraries we now get:
> libfreeradius-radius-2.0.3.la
> libfreeradius-radius-2.0.3.so
> libfreeradius-radius.a
> libfreeradius-radius.la
> libfreeradius-radius.so
>
> Even better, really. Ugh, indeed.
Did you check if that's not some libtool-related problem?
Theoretically the upstream might actually want to start shipping out
one of those two as a real shared library, but wanting is one thing... :)
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
