From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: azamat.hackimov@gmail.com
Subject: Re: [gentoo-dev] RFC: Adding ParaType Free Font License to tree
Date: Wed, 25 Apr 2012 07:53:09 +0200 [thread overview]
Message-ID: <20375.37189.178835.86656@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <CAB_KkxwMtria4zsqEjoAReFnhQa1aTj9Yd2r5vV5Dj82kCF8-A@mail.gmail.com>
>>>>> On Tue, 24 Apr 2012, Maxim Koltsov wrote:
> We had Paratype fonts in tree for some time (media-fonts/paratype)
> with OFL license. Recently they added bold font variant to PTMono font
> with their own license [1], but OFL font tarball was left unchanged.
> We tried to reach upstream with this question, but as for now no
> answer was got.
> So the question is: can Paratype FreeFont license be added to tree as
> /usr/portage/licenses/paratype?
I don't see any reason why it couldn't.
It looks like a simplified version of the OFL license, so it could
even be included in @MISC-FREE in profiles/license_groups.
Ulrich
> [1] http://www.paratype.com/public/pt_openlicense_eng.asp
next prev parent reply other threads:[~2012-04-25 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 19:03 [gentoo-dev] RFC: Adding ParaType Free Font License to tree Maxim Koltsov
2012-04-25 5:53 ` Ulrich Mueller [this message]
2012-04-25 9:58 ` Maxim Koltsov
2012-04-25 11:47 ` Ulrich Mueller
2012-04-25 15:36 ` Maxim Koltsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20375.37189.178835.86656@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=azamat.hackimov@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox