Hi Petr,
how about generating this Oracle header automatically from variable in
Makefile? That way it could be added also into IPS manifest file for
other processing...
Unfortunately I don't think this would be approved. A couple of months
ago, we had a scenario where we wanted to have the three versions of
the GNU Free Documentation license (1.1, 1.2 and 1.3) saved as "template"
files, somewhere in the Userland source workspace, and then included into
the component licenses as appropriate (rather than have the same text
directly in each separate license). The follow-on from that is that we
could
do something similar with GPLv2, GPLv3 and a load more"standard" license
types, and our license files would shrink dramatically, and be much easier
to maintain.
We passed it by legal, and it was not accepted. Our legal person wanted to
see all required license text directly included in the license files.
Therefore I'm doing exactly that for these license file changes and not
considering any alternatives.
As you see there are few projects which are taking license directly
from source archive (ligtttpd). And I think it's quite handy. The
other option to save this would be to allow beside 'license' option in
p5m file also 'license-header' or something like this.
Yeah I saw that. Sorry, but I really don't like it. As well as what I
mention
above, the license file needs to reflect *exactly* what's in the License
Approval section of the Third Party Tracking Tool. Now this may or may
not match what's in the COPYING file provided with the source tar bundle,
but I'd prefer to keep them separate. This is the approach we've taken
with virtually every Userland component.
It also really needs to be in a place where it's easy for the legal person
to be able to review it and make sure it's correct without having to do a:
$ gmake prep
in the component directory, in order to download the source tarball and
unpack it, just so they can see the license file.
It would also be nice to get a consistent naming scheme
(i.e. <component_name>.license), but that's a separate issue.
Thanks for the feedback.
But the first option would be better...
Thanks,
Petr
On 03/ 7/12 10:15 PM, Rich Burridge wrote:
Hi all,
Could I please get a code review for:
7085609 openexr and ilmbase need license file upgrade
http://monaco.us.oracle.com/detail.jsf?cr=7085609
7085613 libmng needs license file upgrade
http://monaco.us.oracle.com/detail.jsf?cr=7085613
7085624 lighttpd needs TPNO and license file modifications
http://monaco.us.oracle.com/detail.jsf?cr=7085624
7085966 iperf needs TPNO and license file modifications
http://monaco.us.oracle.com/detail.jsf?cr=7085966
7085948 swig needs TPNO and license file modifications
http://monaco.us.oracle.com/detail.jsf?cr=7085948
7085963 tcpdump needs TPNO and license file modifications
http://monaco.us.oracle.com/detail.jsf?cr=7085963
7085967 Lua needs TPNO and license file modifications
http://monaco.us.oracle.com/detail.jsf?cr=7085967
7123118 libxslt needs TPNO and license file modifications
http://monaco.us.oracle.com/detail.jsf?cr=7123118
7123119 libxml2 needs TPNO and license file modifications
http://monaco.us.oracle.com/detail.jsf?cr=7123119
7133262 areca needs TPNO and license file modifications
http://monaco.us.oracle.com/detail.jsf?cr=7133262
7151922 autogen needs TPNO and license file modifications
http://monaco.us.oracle.com/detail.jsf?cr=7151922
Webrev is at:
http://jurassic.sfbay/~richb/TPNO_changes-v1/
Userland workspace is at:
/net/stard.us.oracle.com/tank/ws/UL/TPNO_changes/
There is a build/publish log called 'publish-trans.txt' in each
component directory that changed.
Alert viewers will note that all of these entries in the Oracle Third
Party tracking tool are currently in a pending approval state. I spoke
with Fred on this. He said it's fine to add the TPNO # etc to the
license file even though the approval is pending.
Thanks.
_______________________________________________
userland-discuss mailing list
userland-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
_______________________________________________
userland-discuss mailing list
userland-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
_______________________________________________
userland-discuss mailing list
userland-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
