>From a technical standpoint presuming the GPL licence allows it (I'm not a
lawyer and I don't pretend to be one) you might want to consider something
like OpenIntents.
http://code.google.com/p/openintents/
This could allow you to link two unrelated packages together in theory (I
think).
On Sun,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/25/10 22:53 , Anton Persson wrote:
> Well, to connect to a MySQL database you need a connector, and the
> connector library shipped with MySQL is under GPL. Which is what I
> meant. And, hence, corporations buy licenses from MySQL to avoid
> havin
As far as I recall, GPL3 closed the loophole on the specific case that
Naveen outlined, as this was considered not in the spirit of GPL2. People
were using remote connections get around the concept of binary linking. I
only read one of the early drafts, not sure if that was in the final.
On Fri,
Well, to connect to a MySQL database you need a connector, and the connector
library shipped with MySQL is under GPL. Which is what I meant. And, hence,
corporations buy licenses from MySQL to avoid having to release their
applications under the GPL. (If you still don't believe me, try explaining
t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/23/10 10:51 , Sean Hodges wrote:
> You really need to consult a specialist on this subject, developers
> (including me) have a tendency to give out "I am not a lawyer" type
> advice, which is inherently unreliable.
>
> In the strategy you describe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/25/10 04:55 , Andy Savage wrote:
> I forgot to say in my previous post.
>
> In response to the person talking about MySQL. I believe this is
> quite different as MySQL is a completely self contained database
> system that other applications commun
On Tue, Jun 22, 2010 at 11:32 PM, Naveen Maheshwari wrote:
> Yeah David is right.If you link your application with open source libraries
> you have to open your code.
>
> This is not necessary if you're talking about "open source libraries" in
general. They are plenty of open-source license that a
I forgot to say in my previous post.
In response to the person talking about MySQL. I believe this is quite
different as MySQL is a completely self contained database system that other
applications communicate with. As in, it's a completely GPL package, rather
than a part of another application.
Ignoring the legal ramifications here. Let me say my opinion.
I think that we need to be quite wary of the licences of each app and
whether they are conforming to it. Obviously this person intends to try and
not conform to it (if they can figure out how).
But let me give you an example of why thi
That scam won't be legal unless the license in question is the LGPL
(with an L at the front). You say that what you are interested in
using is a library. Typically, libraries use the LGPL since it just
makes sense that libraries allow closed source components to link to
them (L is for LIBRARY), how
You really need to consult a specialist on this subject, developers
(including me) have a tendency to give out "I am not a lawyer" type
advice, which is inherently unreliable.
In the strategy you describe, I believe putting A and B in the same
APK means you are distributing both components as a si
Yeah David is right.If you link your application with open source libraries
you have to open your code.
That's why what I am trying to do is the code that uses open source I make
it as separate module and run that as remote service.
Now since this service is running as a separate process so I am
I think david is very right about that.
On Wed, Jun 23, 2010 at 4:04 PM, David Turner wrote:
>
>
> On Tue, Jun 22, 2010 at 9:33 PM, HaMMeReD wrote:
>
>> If you can use it without modifying the source then just do it, and
>> provide credit to the library creator clearly in your app.
>>
>> this i
On Tue, Jun 22, 2010 at 9:33 PM, HaMMeReD wrote:
> If you can use it without modifying the source then just do it, and
> provide credit to the library creator clearly in your app.
>
> this is wrong on many levels. As soon as you *distribute* the binaries
(e.g. through Market),
you must provide th
I am not a lawyer too. But basis on my understanding, for LGPL and Apache
License v2.0, you can use use them in closed source application if you do
not have any modifications. For GPL, you cannot use them in a closed source
application.
On Wed, Jun 23, 2010 at 2:33 PM, HaMMeReD wrote:
> If you
If you can use it without modifying the source then just do it, and
provide credit to the library creator clearly in your app.
If you need to modify the source, then you need to be able to provide
the modifications. If you need to integrate it with your app deeply so
that you can't use the modifie
16 matches
Mail list logo
