license_noconflict ignored on builders?
Jason Liu
jasonliu at umich.edu
Sat Jan 15 00:14:36 UTC 2022
Oh, was license_noconflict supposed to be used with the name of a port? I
thought it was supposed to specify a license that didn't conflict!
--
Jason Liu
On Fri, Jan 14, 2022 at 6:35 PM Joshua Root <jmr at macports.org> wrote:
> On 2022-1-15 03:58 , Jason Liu wrote:
> > I added a license_noconflict
> > <https://github.com/macports/macports-ports/pull/13641> to one of my
> > portfiles a couple of days ago, and it appears that the builders are
> > still flagging it as not distributable:
> >
> > "warzone2100" is not distributable because its license "gpl" conflicts
> > with license "OpenSSL" of dependency "openssl11"
> >
> > Is it possible that the license_noconflict is being ignored?
>
> The Portfile says "license_noconflict openssl". It doesn't say
> anything about openssl11.
>
> Looking at the explanation in the comment, it looks like you actually
> mean "license_noconflict asciidoctor"?
>
> - Josh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20220114/f73feee6/attachment.htm>
More information about the macports-dev
mailing list