On 08/20, Stuart Henderson wrote: > The ports read OK but have you considered keeping the Apache-licensed one > in the same PKGNAME as before (so that pkg_add -u works), and picking a > different name for the non-free one? (funny looking license, I don't > have the energy to read it all but "do not hack the licensing mechanism" > sticks out as strange text to use!) Yes, my first approach was exactly like that, but it clashes with official naming, i.e. Elastic uses *-oss naming for Apache-licensed packages and I'd like to avoid ambiguity. Not sure how to deal with updates, e.g. how to manage it via quirks. Any suggestions?
-- With best regards, Pavel Korovin