On Mon, Apr 20, 2009 at 2:32 PM, Alain Baeckeroot <[email protected]> wrote: >> == >> The source code for a work means the preferred form of the work for >> making modifications to it. For an executable work, complete source >> code means all the source code for all modules it contains, plus any >> associated interface definition files, plus the scripts used to >> control compilation and installation of the executable. However, as a >> special exception, the source code distributed need not include >> anything that is normally distributed (in either source or binary >> form) with the major components (compiler, kernel, and so on) of the >> operating system on which the executable runs, unless that component >> itself accompanies the executable. >> == >> >> In other words, you can link against VC++ runtime libs, but you can't >> include them into an installer for user convenience. >> >> Michael. >> > out of curioisity too, doesn't this affect all GPL2 modules and > octave itself ?
Possibly yes, but I guess this depends on your interpretation of the last sentence of the quoted paragraph. > doesn't shipping on 2 different media would solve the problem ? Anybody is free (as in free speech) to redo the port, compilation and packaging of more than 50 components, if he wants to. Michael. ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
