Date: Mon, 25 Aug 2014 17:31:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 187926] New port: devel/liballium - Tor pluggable transports utility library Message-ID: <bug-187926-13-UGjpLqvRtd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-187926-13@https.bugs.freebsd.org/bugzilla/> References: <bug-187926-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187926 --- Comment #24 from Adam Weinberger <adamw@FreeBSD.org> --- (In reply to John Marino from comment #23) > (In reply to fk from comment #22) > > I wouldn't mind LICENSE_FILE being set to the path of the file that, > > according to upstream, contains the license that is relevant, but my > > impression is that LICENSE_FILE only works together with LICENSE and the > > latter is a claim I'm not interested to make (except for the few upstream > > commits I did myself). > > Each variable is independent. If you define LICENSE_FILE, you get that > exact license. In fact, that is what @mat wants all ports to do. The whole of bsd.licenses.mk is wrapped in .if defined(LICENSE). Using LICENSE_FILE with an unknown license also requires breaking down the license into LICENSE_PERMS. Submitter is correct that it isn't as easy as just defining LICENSE_FILE and being done with it. There is no officially sanctioned location for licenses. Thousands of other ports install their license file into DOCSDIR, and this port does the same. Fabian, if you believe that the COPYING file should go back into ${PREFIX}/share/licenses where you originally had it, I am fine with moving it there instead. Past that, I agree with you that LICENSE* is ambiguous. I'll leave the decision up to you, I am happy to move the file to share/licenses or leave it as-is and close this PR. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-187926-13-UGjpLqvRtd>