On Sun, Jul 15, 2012 at 8:17 PM, Juergen Weigert
I know. Let me refer to on of the documents published by the SFLC. http://www.softwarefreedom.org/resources/2008/compliance-guide.html It discusses the effort in detail, and summarizes like this: ... you must include “scripts used to control compilation and installation of the executable” and/or anything “needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities”. These phrases are written to cover different types of build environments and systems. Therefore, the details of what you need to provide with regard to scripts and installation instructions vary depending on the software details. You must provide all information necessary such that someone generally skilled with computer systems could produce a binary similar to the one provided.
While that is true, it's part of the license, the point in my earlier post is that those phrases don't refer to obs scripts, they refer to makefiles and configure scripts that are already part of the source rpms, inside the tarballs. You can build using only those scripts, provided you've installed all the dependencies. It's not the spirit of the GPL that the distributor should provide absolutely everything, otherwise people would be forced to give you the hardware and operating system used to build (as that can influence build results, as is notoriously true in the atlas package). No, the scripts mentioned in the GPL are already there on the tarball. All the other stuff openSUSE provides are conveniences, not necessary for GPL compliance. That's my humble understanding of the words. IANAL. Maybe a lawyer could shed some light into this thread, though, knowing them (my dad's one), I imagine they'd just add more questions and uncertainty instead. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org