license_noconflict ignored on builders?

[Jason Liu]

Yes, I went back and re-read that before I posted. The second example might
qualify as having answered my question, but since "openssl" is both the
name of a port and one of the licenses, maybe that's not the best example
to be using? Especially considering that the keyword just above
"license_noconflict" is "license", and the second example in that entry
uses "freetype", which again is both the name of a port and one of the
licenses.

-- 
Jason Liu


On Fri, Jan 14, 2022 at 7:23 PM Ryan Schmidt <ryandesign at macports.org>
wrote:

> On Jan 14, 2022, at 18:14, Jason Liu wrote:
>
> > 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!
>
> See the documentation for license_noconflict at
>
> https://guide.macports.org/#reference.keywords
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20220114/3e624861/attachment-0001.htm>