https://bugzilla.novell.com/show_bug.cgi?id=670050 https://bugzilla.novell.com/show_bug.cgi?id=670050#c wei wang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wewang@novell.com AssignedTo|bnc-team-screening@forge.pr |mls@novell.com |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=670050 https://bugzilla.novell.com/show_bug.cgi?id=670050#c2 --- Comment #2 from Juergen Weigert 2011-02-15 11:35:54 UTC --- Subpackages can have their individual License: tag. Just the source package does not support this. I envision two possible implementations: A new tag SourceLicense: that allows to specify a license string exclusively for the source rpm. Similar concept like BuildRequires are Requires for sources. A macro that gets evaluated only when sources are built. Assume a package foo - with complex python based build scripts, licensed under a Python license. - with a comprehensive cucumber test suite licensed under X11 MIT license. - with a GPL'ed source tar ball containing Documentation under GFDL. I'd like to say something like this: Name: foo Version: 1.0 License: GPLv2+ SourceLicense: GPLv2+; GFDLv1.1; Python; X11 MIT %package doc License: GFDLv1.1 %files ... /usr/bin/* %files doc /usr/share/doc/* Where the build scripts and test suite do not enter the binaries or documentation packages. The expected outcome is $ rpm -qp --qf '%{License}\n' RPMS/*/foo-1.0.*.rpm GPLv2+ $ rpm -qp --qf '%{License}\n' RPMS/*/foo-doc.1.0.*.rpm GFDLv2.1 $ rpm -qp --qf '%{License}\n' SRPMS/foo-1.0.*.src.rpm GPLv2+; GFDLv1.1; Python; X11 MIT -- 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.