https://bugzilla.novell.com/show_bug.cgi?id=183725#c18
--- Comment #18 from Ciaran Farrell 2007-11-30 02:47:22 MST ---
If you mean the openSUSE EULA, then this does 2 separate things:
(1) explicitly point out that individual component packages' license take
precedence over the EULA (e.g. xsane GPL license)
(2) add a Novell disclaimer to cover the entire "collective work"
Given that this issue is covered by (1), the GPL need not be explicitly
accepted by click through license. See http://www.gnu.org
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible
use to the public, the best way to achieve this is to make it free software
which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach
them to the start of each source file to most effectively state the exclusion
of warranty; and each file should have at least the “copyright” line and a
pointer to where the full notice is found.
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see http://www.gnu.org/licenses/.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short notice like
this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands might
be different; for a GUI interface, you would use an “about box”.
See also GPLv2 Section 0:
Activities other than copying, distribution and modification are not covered by
this License; they are outside its scope. _The act of running the Program is
not restricted_, and the output from the Program is covered only if its
contents constitute a work based on the Program (independent of having been
made by running the Program). Whether that is true depends on what the Program
does.
Note, however that DISCLAIMING WARRANTIES IS NOT AS SIMPLE AS PUTTING IN A
NOTICE OF DISCLAIMER - many jurisdiction have enacted legislation to limit the
effect of such disclaimers. Therefore, it is necessary to check in your own
jurisdiction, to see if such a disclaimer is effective.
Thus, for the purposes of the GPL, the user should be made aware of his/her
rights - this does not have to be done by way of a pop up license text - the
GPLv2 itself explicitly states: "Of course, your program's commands might be
different; for a GUI interface, you would use an “about box”. Of course,
the GPL text itself must also be provided in the package.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.