-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Mittwoch, 9. September 2009 23:30:19 schrieb Hans Aberg: > The point is that if you want to be up-to-date with latest GPL in both > new restrictions and permissions, the only way to do it is to refer to > the latest version when the source is published. "Or later" will admit > later restrictions, "or latest" will impose them quietly on old sources.
... which I'm sure will NOT hold up in court, so I propose we really end this discussion. Please leave the lawyering to the lawyers and lets go back to coding. Cheers, Reinhold PS: The "or latest" would also be the perfect weapon for anyone trying to spread FUD about open source, since now a third person (the FSF) has basically control about your code (i.e. it can now make your investments into open source suddenly illegal). Tell (or simply mention it slightly) that to any manager, and you can be sure that Open Source will be ruled out forever in that company. Imposing additional restrictions quietly on old sources is a big legal NO-NO. - -- - ------------------------------------------------------------------ Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFKqCPiTqjEwhXvPN0RAt2VAKDOe4G1/GBSi9n2T7vLH3LUVUnaLwCfQNIz 4I5WosJyvY3S3hS9xds4lL4= =c3MS -----END PGP SIGNATURE----- _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
