I recommend using either "open_source", "unrestricted", "restrictive", or "unknown", by
looking at the documentation for each and deciding which one matches your intent best, and
then using the "meta_merge" feature (or hand-editing the META.yml file) to point to a URL
containing the exact text of the license you'd like to use. In accordance with the META.yml
spec (
http://module-build.sourceforge.net/META-spec-blead.html#resources), it would look
like this:
resources:
license:
http://example.org/your-license.txt
MailingList:
http://hop.perl.plover.com/#mlist
That seems flexible enough to me, or is there some issue I'm not thinking about?
-Ken