Date: Wed, 26 Jan 2011 02:08:17 -0800 From: Charlie Kester <corky1951@comcast.net> To: freebsd-ports@FreeBSD.org Subject: Re: Should I be adding LICENSE info to my ports? Message-ID: <20110126100817.GA34311@comcast.net> In-Reply-To: <20110126101350.ae448a5f.ehaupt@FreeBSD.org> References: <20110126001729.GA70944@comcast.net> <20110126034636.GB19985@magic.hamla.org> <20110126101350.ae448a5f.ehaupt@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed 26 Jan 2011 at 01:13:50 PST Emanuel Haupt wrote: >Sahil Tandon <sahil@freebsd.org> wrote: >> On Tue, 2011-01-25 at 16:17:29 -0800, Charlie Kester wrote: >> >> > Today on FreshPorts I see some bulk commits adding LICENSE info to >> > 40+ ports. And I've noticed LICENSE being added in many other recent >> > commits. >> >> Right, ehaupt@ updated several of his ports to include LICENSE. > >I was very reluctant to do so but now that the license framework has >been around for some time I thought I give it a go. > >As Sahil pointed out it's entirely up to you. Better have no license >specified if you're not sure about it. You can not always trust the >included COPYING file. There are many cases where a port comes with >several different licenses. I found that cross checking with different >linux distros could often bring some clarification. Good tips, thanks. There's also often some licensing info in the author's manpage, website, or other documentation. I'm not going to submit a flurry of PR's to add this to all my ports, but I will begin gathering the info so I can include it as part of any other updates.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110126100817.GA34311>