ports licenses
in [Ports]
|
From: Rene Ladan on 30 May 2010 16:20 Hi, While adding license information to my ports (to be committed), I stumbled upon the following: * devel/argouml uses Eclipse Public License (EPL) 1.0, but this one is not in bsd.licenses.db.mk * lang/bas2tap uses some homebrew license, but it has no formal name, so LICENSE_NAME cannot be formally set. I think the first one can be added to bsd.license.db.mk, but I'm not sure what to do about the second one. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Eitan Adler on 30 May 2010 17:00 On Sun, May 30, 2010 at 11:20 PM, Rene Ladan <rene(a)freebsd.org> wrote: .... > * lang/bas2tap uses some homebrew license, but it has no formal name, so > LICENSE_NAME cannot be formally set. > > I think the first one can be added to bsd.license.db.mk, but I'm not > sure what to do about the second one. from bsd.licenses.mk # Case 2: license only known by the port (aka "unknown"). # # In this case LICENSE_{PERMS,NAME} are mandatory, in addition to # either LICENSE_FILE or LICENSE_TEXT. Optional variables are # LICENSE_{GROUPS,NOTES}. -- Eitan Adler _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Charlie Kester on 30 May 2010 17:29 On Sun 30 May 2010 at 13:20:55 PDT Rene Ladan wrote: >Hi, > >While adding license information to my ports (to be committed), I >stumbled upon the following: Is this something all maintainers should be doing? Yesterday, while upgrading my installed ports, I noticed a message in the output about LICENSE not being defined. I also see that there's now a bsd.licenses.mk and a bsd.licenses.db.mk in /usr/ports/Mk. I don't recall seeing those before, and don't know how long they've been there. Anyway, it looks like we're going ahead with this infrastructure, and I think that's a good thing. What actions do you need from me as a maintainer? _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Wesley Shields on 30 May 2010 17:40 On Sun, May 30, 2010 at 02:29:45PM -0700, Charlie Kester wrote: > On Sun 30 May 2010 at 13:20:55 PDT Rene Ladan wrote: > >Hi, > > > >While adding license information to my ports (to be committed), I > >stumbled upon the following: > > Is this something all maintainers should be doing? > > Yesterday, while upgrading my installed ports, I noticed a message in > the output about LICENSE not being defined. I also see that there's now > a bsd.licenses.mk and a bsd.licenses.db.mk in /usr/ports/Mk. I don't > recall seeing those before, and don't know how long they've been there. > Anyway, it looks like we're going ahead with this infrastructure, and I > think that's a good thing. > > What actions do you need from me as a maintainer? They are both fairly new constructs. I don't recall exact dates but they are new enough that the documentation for them has not caught up yet that I'm aware of. I'd wait until the Porter's Handbook is updated for further clarification on what to do. I'd also say that if you have a regular update planned for a port that you submit the license information with that. -- WXS _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Charlie Kester on 30 May 2010 17:59 On Sun 30 May 2010 at 14:40:38 PDT Wesley Shields wrote: > >I'd also say that if you have a regular update planned for a port that >you submit the license information with that. Yeah, phasing it in along with other work makes sense. /visions of 20,000+ new PR's doing nothing but adding LICENSE info _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
|
Next
|
Last
Pages: 1 2 Prev: Ports on Clang [SOLVED] Next: Issue with recent license infrastructure. |