| |||||||||||||
|
| |||||||||||||
The FSF warns (again) against MonoThe FSF warns (again) against MonoPosted Jul 19, 2009 21:10 UTC (Sun) by directhex (subscriber, #58519)In reply to: The FSF warns (again) against Mono by rahulsundaram Parent article: The FSF warns (again) against Mono
Which leaves only one real sticking point - ADO.NET, the System.Data namespace.
So. In your considered legal opinion, what needs to be done to make SQlite access "safe"? Which specific details of System.Data make it dangerous? What do apps need to do? Is renaming it to "Panda.Data" enough for all legal risk to suddenly vanish, in your mind? If not, what do you suggest instead?
(Log in to post comments)
The FSF warns (again) against Mono Posted Jul 20, 2009 7:40 UTC (Mon) by rahulsundaram (subscriber, #21946) [Link]
I suggest contacting SFLC if you must continue using Mono
The FSF warns (again) against Mono Posted Jul 20, 2009 8:58 UTC (Mon) by kragil (guest, #34373) [Link]
Nice try, but mono evangelists are not really into real legal advice.
They prefer to make it up themselves.
The FSF warns (again) against Mono Posted Jul 20, 2009 9:22 UTC (Mon) by directhex (subscriber, #58519) [Link]
Oh, and that's your considered legal opinion is it?
The FSF warns (again) against Mono Posted Jul 20, 2009 9:31 UTC (Mon) by rahulsundaram (subscriber, #21946) [Link]
If you want legal opinions ask the lawyers. That's my non legal opinion :-)
|
|
||||||||||||