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 this in general is a bad idea. I have gone through some trouble to try and find a way to play DivX/xVid on Android for my app and I think that much of my time and trouble wouldn't have been wasted if people were more strongly conforming to the software that licences are released under. Take RockPlayerBase for example, this app (which is in "beta") plays DivX and xVid. It's not magic, it simply does this by ffmpeg (I can tell by checking the library names in the pcakge). I have no website (in English atleast) to request this, but when it gets released I will be requesting they they conform to the LGPL source and release instructions on how they compiled it for android and the changes (if any) they made. Whats really frustrating is that they didn't release these instructions at the same time as their app. Now this is just one example but I am sure other apps will be using opensource technologies that are designed to share knowledge. Sometimes alot of trouble can be needlessly wasted when others refuse to conform or try to avoid the good spirit licences. Consider this when trying to sidestep GPL. It's there for a specific reason, I can understand you wanting to keep proprietary code secret, but generally my experience is most of the code could be happily released. Unless your a rocket scientist it's likely something that could be of use to others, who could in turn make changes which you can incorporate and so on. *However all is not lost*, if you are looking to find a way to incorporate some open code. Ask if the authors might release it under dual licence as LGPL for you. A great example of how this can work is Bambuser<http://www.bambuser.com/opensource>. A proprietary program but they use ffmpeg and conform to LGPL licence. It doesn't hurt their business or product and they have made life alot easier for those who are simply trying to get stuff to work. On Tue, Jun 22, 2010 at 11:44 PM, a genius <droidhac...@gmail.com> wrote: > 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), however, there are still some nasty issues > that are present.... such as the ability of the USER to REPLACE the > LGPL LIBRARY with a newer version of the same library.... to your > benefit, it doesn't have to be TRIVIAL to do so, so NDK within the > same APK should suffice -- build the LGPL library into your program > using the NDK, you will end up with a shared object file that is > licensed as LGPL, which happens to be distributed along with your > proprietary program in the archive container. Be sure to include a > COPY OF THE LGPL LICENSE ALONG WITH THE LIBRARY and to be sure to > identify what library it applies to. ALSO be sure to make notice > WITHIN THE PROGRAM ITSELF that (A) you use LGPL components, (B) what > the LGPL components are. > > If the library is licensed regular GPL, then NO, you MAY NOT use it. > And no, a wrapper program DOES NOT avoid this issue since the entire > purpose of the wrapper is clearly to avoid the GPL. > > On Jun 22, 3:10 am, Naveen <naveen...@gmail.com> wrote: > > Hi! > > I need to use some open source code with GPL3. > > > > As usual I don't want to open source code for full application. > > > > Now what I understand is if I make two separate process one with my > > main application code and other as a service or something with Open > > source library then in that case I have to open source code only for > > the other one. > > > > Now the question is what is the best way to do so in Android. > > > > Suppose > > My Main App is A > > Open Source code is B > > > > So A will give some data to B. B will process this and sends data back > > to A. B may not need to have any UI. > > > > 1. Is it possible to install 2 seperate applications / processes from > > one APK? > > 2. What is the best way ?Should B be a service? How will be the > > communication between A and B ? > > 3. Is it possible to run/call B from A? > > > > Pls. advice > > > > Thanks > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
