Patents on the other hand pertain to a method of doing something (separate from actual code) and are far from certain and vary widely between jurisdictions. The outcomes are decided in local courts based on a mix of precedent and who can spend the most on lawyers.
In short, copyrights and patents have nothing whatsoever to do with each other.
You are correct that software patents can be nebulous. However, in the case of codec patents, like that of H.264, the new MPEG video standard, SCOTUS and patent cases have routinely upheld the validity of similar software patents.
For an overview of relevant statutes, I would point to the USPTO documents, which outline the standards that most software patents are viewed under (by the USPTO and many practicing US patent lawyers)[1]. While In re Bilski[2], recently granted a writ, may present a new view on some of the more spurious (and business-oriented) software patents, it seems that SCOTUS is more than willing to uphold the patents in practical implementation cases[3][4][5].
If this were a discussion based purely on ideology then upholding copyright but ignoring patent rights may be defensible, however to suggest that they will bring legal action to defend their copyright but to ignore or refuse that they should be held accountable in patent litigation is a tad hypocritical.
[1] http://www.uspto.gov/web/offices/pac/mpep/documents/2100.htm
[2] http://www.cafc.uscourts.gov/opinions/07-1130.pdf
[3] http://www.oyez.org/cases/1980-1989/1980/1980_79_1112/
Also, most of the developers are based in Europe, where software patents are much more dubious than in the US.
Most? I was aware that many were, but I know at least a couple are not. However, in my first comment I was very clear that I was speaking only to US developers -- Europeans, feel free to ignore.
Patents do not apply to the developers, they apply to the users of the software
Not in the United States. "Except as otherwise provided in this title, whoever without authority makes, uses, offers to sell, or sells any patented invention, within the United States or imports into the United States any patented invention during the term of the patent therefor, infringes the patent."[1]
On the other hand, distributors of binaries do have to take into account patent laws.
Edit: By the way, don't be fooled, our small legal disagreement doesn't affect my very positive view of you as a person and developer :)
"Under certain jurisdictions, there is a particular case of patent infringement called "indirect infringement." Indirect infringement can occur, for instance, when a device is claimed in a patent and a third party supplies a product which can only be reasonably used to make the claimed device."
http://en.wikipedia.org/wiki/Contributory_patent_infringemen...
If it had extra requirements, it wouldn't be using the LGPL (and I don't think it would even be compatible). Those are just restatements of parts of the license; you can see which sections just by reading it, as it's quite short.
The main difference between the GPL and the LGPL is that the latter can be linked to (in the case of a library, 'used by') a non-(L)GPLed program, and regardless of whether it is free software or proprietary software.[1] This non-(L)GPLed program can then be distributed under any chosen terms if it is not a derivative work. If it is a derivative work, then the terms must allow "modification for the customer's own use and reverse engineering for debugging such modifications."
I'm not arguing that the FFMPEG folks don't deserve respect and adherence to their license terms. Just seems like they aren't really helping themselves here either. If you make a situation confusing you cannot be angry when people get confused. My personal feeling is if you want to do "free software" you should remember the whole free part. The GPL and it's variants are too overtly political for my tastes. The BSD license seems a bit more intellectually honest.