[issue732] LGPL violation Cycorder, Qik
Diego Biurrun di...@biurrun.de added the comment: On Sun, Jan 11, 2009 at 07:31:56PM +, Jay Freeman (saurik) wrote: Jay Freeman (saurik) sau...@saurik.com added the comment: Diego Biurrun di...@biurrun.de added the comment: How do you compile/restrict FFmpeg? Once again, I don't restrict it, can't restrict it, don't claim I should restrict it, nor understand why you or Michael persist in that belief. I'll rephrase: What is your configure line, what do you enable or disable? What conversations are you referring to? FFmpeg has been in Debian since the dawn of time more or less. MPlayer has been in Debian for a few years as well now. http://lists.debian.org/debian-legal/2005/06/msg00241.html Andrew Suffield is a flaming troll, to put it mildly. This message proves nothing. As I said, FFmpeg has been in Debian since what feels like the dawn of time, MPlayer since a long time already. Diego FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
[issue732] LGPL violation Cycorder, Qik
Jay Freeman (saurik) sau...@saurik.com added the comment: Diego Biurrun di...@biurrun.de added the comment: How do you compile/restrict FFmpeg? On Sun, Jan 11, 2009 at 07:31:56PM +, Jay Freeman (saurik) wrote: Once again, I don't restrict it, can't restrict it, don't claim I should restrict it, nor understand why you or Michael persist in that belief. Diego Biurrun di...@biurrun.de added the comment: I'll rephrase: What is your configure line, what do you enable or disable? I'm sorry, but I don't understand why are insisting to keep asking me questions down this path. What is your goal? Are you trying to get me to reconsider? Please provide a thesis so I know whether its worth my time to be in this argument that I didn't even start. I stated my intention, I provided one side effect at least I won't have to deal with this particular problem anymore, and now you won't leave me alone. I don't need to support your software, I don't want to support your software, and I definitely don't have to sit here answering your questions about the methods by which I used to support your software. If you really care so much, go look it up in the Telesphoreo repository (I'm not going to delete the directories for it until I'm totally through with it), but leave me out of it. -J FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
[issue732] LGPL violation Cycorder, Qik
Jay Freeman (saurik) sau...@saurik.com added the comment: Michael Niedermayer michae...@gmx.at added the comment: baseline jpeg (not arithmetic coded) yes possibly it is free of patents, though strictly speaking noone stops a new person to come forth with a new patent that might be valid according to the law, this is very unlikely but its not impossible ... But (m)jpeg has a very poor quality per bitrate even compared to mpeg1, it is thus surely understandable if users ask you to support something better. So i think diego did not consider such joke codecs. About not supporting anything except jpeg, you cannot while using *GPL as the user always has the right to remove such restriction, like recompiling ffmpeg with a full set of codecs. You surely can choose not to use *GPL code and maintain any set of restrictions with your own self written jpeg code. But then you are offering people who have a aircraft ticket a rowboat one to cross the atlantic. Thats fine, just ridiculous. You are confusing requests to Cycorder with requests to Telesphoreo. Telesphoreo is a distribution of Unix, such as Debian, for mobile platforms (really: the iPhone). It maintains and supports a distribution of FFmpeg for the iPhone, and is what is used on all jailbroken iPhones (over a million of them at this point). I, as the primary maintainer of Telesphoreo (and the listed maintainer for FFmpeg), get requests constantly from people for supporting more codecs in my distribution. Of course I cannot keep them from compiling their own copy, no one ever claimed as much. Your comments about GPL, therefore, have nothing at all to do with what Telesphoreo /ships/. If you seriously believe that Telesphoreo /must/ distribute all kinds of codecs /just/ because it is possible, then maybe that explains why both this project and Mplayer have had such miserable luck negotiating with Debian over getting their projects included. (Conversations I have read through in detail in the attempt to understand whether or not Telesphoreo should be bothering.) If a user wants to recompile FFmpeg and use it, turning on support for all possible codecs, patents be damned, let him go head. You simply made up restriction here: that was never in my argument. FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
[issue732] LGPL violation Cycorder, Qik
Michael Niedermayer michae...@gmx.at added the comment: On Sat, Dec 27, 2008 at 04:27:05AM +0100, Michael Niedermayer wrote: On Fri, Dec 26, 2008 at 04:56:36PM +, Nick wrote: [...] Also, can you please kindly remove my email address shown explicitly in your message? just not to risk it getting picked up by spam crawlers. You can ask luca barbato, but chances are its too much work to just figure out how to remove it. And yes i would remove it if i knew how and it was simple but i dont even know how. Also its not my fault if you use a valuable address on a public tracker / public forum / public mailing list. So unless you either know how we can blank the address out and its simple, have some volunteer to help us admin this tracker or something else. Iam sorry but iam not going to spend hours to find a way to remove an address you entered. Besides this, its not enough to remove it from the tracker, theres a mailing list behind it and thats archived on gmane (probably amongth other places) so there are likely a dozen places on half a dozen different servers some of which we dont even know nor have write access to. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB When you are offended at any man's fault, turn to yourself and study your own failings. Then you will forget your anger. -- Epictetus FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
[issue732] LGPL violation Cycorder, Qik
Nick n...@qik.com added the comment: Every time you push a new version, you need to provide the *exact* same source that was used to build that version. So you better start putting such a system in place now, the longer you wait, the more difficult it will get. I understand this, my point was that this requires some manual synchronization, unless we keep modified sources only in public repository, which is not convenient in the light of intermediate not-public builds. In any case, we prefer to go thru email requests for now, if this is ok. Also, we have the same problem that saurik noted on iphone, we can't use it as dynamically linked lib - so we had to prepare similar object linking package. Saurik is now linking dynamically, at least he said so. What exactly is your problem? I am not sure what Saurik meant by lack of stability with dynamic lib - for us, we just can't build the app package correctly in XCode, so that dynamic lib would get loaded correctly after app runs - seems that this is related with signing - since this dynamic lib is a standalone component, looks like it has to be signed on its own. If someone can help, we definitely would prefer to go dynamic lib route. FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
[issue732] LGPL violation Cycorder, Qik
Michael Niedermayer michae...@gmx.at added the comment: On Fri, Dec 26, 2008 at 04:56:36PM +, Nick wrote: [...] Also, can you please kindly remove my email address shown explicitly in your message? just not to risk it getting picked up by spam crawlers. You can ask luca barbato, but chances are its too much work to just figure out how to remove it. And yes i would remove it if i knew how and it was simple but i dont even know how. Also its not my fault if you use a valuable address on a public tracker / public forum / public mailing list. So unless you either know how we can blank the address out and its simple, have some volunteer to help us admin this tracker or something else. Iam sorry but iam not going to spend hours to find a way to remove an address you entered. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Republics decline into democracies and democracies degenerate into despotisms. -- Aristotle FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
[issue732] LGPL violation Cycorder, Qik
Diego Biurrun di...@biurrun.de added the comment: On Fri, Dec 26, 2008 at 11:56:15PM +, Nick wrote: Nick n...@qik.com added the comment: Every time you push a new version, you need to provide the *exact* same source that was used to build that version. So you better start putting such a system in place now, the longer you wait, the more difficult it will get. I understand this, my point was that this requires some manual synchronization, unless we keep modified sources only in public repository, which is not convenient in the light of intermediate not-public builds. I must say I fail to see your problem. It is not difficult to design a system where you publish a subdirectory or branch or whatever of your internal repository. And it's not difficult to do this automatically. Whether you already have such a system in place is a different issue. But you *will* need it in the future. Producing the exact source for a specific version of your software can become an infinite amount of work if you do not plan ahead... In any case, we prefer to go thru email requests for now, if this is ok. It's OK in light of the license, it will just make your life more difficult. I have already provided you with a first round of comments for the patch you sent me in private. You should eventually submit this on ffmpeg-devel and aim for upstream integration. This will be the best and easiest solution for all parties. Diego FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
[issue732] LGPL violation Cycorder, Qik
Diego Biurrun di...@biurrun.de added the comment: On Thu, Jan 08, 2009 at 10:18:25AM +, Jay Freeman (saurik) wrote: Jay Freeman (saurik) sau...@saurik.com added the comment: (For some reason I only just received these last few e-mails now, which is why this response is so late.) The issue tracker was down and is back online now. Diego: For the record, I never claimed I was now linking dynamically. I said I will do that in the next version of Cycorder, which was to happen after I had finished porting FFmpeg to the iPhone (where porting here is mostly fixing the compiler to support it correctly, work that I will need to do as I'm the only person maintaining the completely open iPhone toolchain). I therefore do not feel like your harsh tone to Nick is even remotely called for. Sorry, I just reread the messages in the tracker, I don't see myself using a harsh tone towards Nick. In any case, I was not intending to do it. If you have some instructions for compiling FFmpeg on/for the iphone, I'd gladly add them or a link to them to our documentation. Regardless, at this point I think it would be easier for everyone, and definitely a faster resolution (as this is dragging on quite a bit), if I simply cease Telesphoreo's involvement in maintaining FFmpeg on this platform and simply rewrite the one container format Cycorder needs (which I can then release seperately under BSD). If nothing else, that will end the patent hell I've been ending up in (I am continually asked to support random patented algorithms in Telesphoreo's codec set, and I'm somewhat sick of it now). Forget about non-patented codecs. They do not exist. Diego FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
[issue732] LGPL violation Cycorder, Qik
Nick n...@qik.com added the comment: just like Saurik, I'm completely lost on how to use this tracker... not sure how to reply correctly. Also, can you please kindly remove my email address shown explicitly in your message? just not to risk it getting picked up by spam crawlers. The URL you use on http://qik.com/info/opensource is outdated, please link to http://ffmpeg.org/ instead of http://ffmpeg.mplayerhq.hu/. no problem, will change shortly. Why don't you simply offer the FFmpeg source code for download? That's much easier for you and for us. I would like to have a look at your tarball. I am not sure what's the best way to put it out for download - in the sense of getting its components automatically updates every time we push new version... and if we just put out static archive, it will get obsolete pretty soon. At the same time, creating separate version control for this is a bit hard, need to set up a publicly accessible server for this. Also, we have the same problem that saurik noted on iphone, we can't use it as dynamically linked lib - so we had to prepare similar object linking package. Diego, what email should I send you the archive? FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
[issue732] LGPL violation Cycorder, Qik
Diego Biurrun di...@biurrun.de added the comment: On Tue, Dec 23, 2008 at 07:34:05PM +, Nick wrote: Nick n...@qik.com added the comment: We recently learned of the posting here about FFmpeg, LGPL and the Qik client software application. We have added the LGPL notices for FFmpeg to our website at http://qik.com/info/terms_of_service and http://qik.com/info/opensource . We also are adding appropriate notices to the corresponding Qik client software application. We apologize for the oversight. If you have any questions or concerns, please feel free to contact me atn i c k at q i k dot c o m The URL you use on http://qik.com/info/opensource is outdated, please link to http://ffmpeg.org/ instead of http://ffmpeg.mplayerhq.hu/. Why don't you simply offer the FFmpeg source code for download? That's much easier for you and for us. I would like to have a look at your tarball. Diego FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
[issue732] LGPL violation Cycorder, Qik
Nick n...@qik.com added the comment: We recently learned of the posting here about FFmpeg, LGPL and the Qik client software application. We have added the LGPL notices for FFmpeg to our website at http://qik.com/info/terms_of_service and http://qik.com/info/opensource. We also are adding appropriate notices to the corresponding Qik client software application. We apologize for the oversight. If you have any questions or concerns, please feel free to contact me atn i c k at q i k dot c o m FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
[issue732] LGPL violation Cycorder, Qik
Steve woob...@gmail.com added the comment: I'm pretty sure Orb Live for iPhone (in the app store and previously on cydia) is using ffmpeg, FYI. FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.ffmpeg.org/roundup/ffmpeg/issue732
