Re: [Rlib-devel] RLIB-1.3.2 questions, problems and an ODBC fix

[Bob D. <bd...@si...>]

>  > This seems wrong to me.  And I hate to have to go into all these details
>  > but the (c) stuff is really important to the company.  I would rather be
>  > coding, trust me ;)
> 
> AFAIK you can include LGPL code into GPL, it becomes GPLed.
> But IANAL. I am good at acronyms. :-)
> 

My problem is that SICOM could no longer sell the commercial version of
RLIB if I put the nl_langinfo stuff in since we won't be able to dual
copy right it.

I take something was was LGPL but turned to GPL and then turn it back to
LGPL.  

Legally I would have the ask the guy who made the nl_langinfo patch to
sign the RLIB (c) form.  I feel kinda silly doing this but I could
always ask.

Other then that I think we are in good shape

> perl -pi.bak -e "s#need_relink=yes#need_relink=no#" ltmain.sh
> 
> into autogen.sh after libtoolize.

Thanks ;)