From: Maxim Koltsov <maksbotan@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 19:36:35 +0400 [thread overview]
Message-ID: <CAB_Kkxy3O+eMPT9xM_L3PJabuFPGHHUqBw7aGooyXR0Zyq+jQg@mail.gmail.com> (raw)
In-Reply-To: <20375.58455.939282.417001@a1i15.kph.uni-mainz.de>
25 апреля 2012 г. 15:47 пользователь Ulrich Mueller <ulm@gentoo.org> написал:
>>>>>> On Wed, 25 Apr 2012, Maxim Koltsov wrote:
>
>>>> 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.
>
>> So, just to clairfy. I create file 'paratype' in gentoo-x86/licenses,
>> paste there text of license and then commit?
>
> Right. If it exists, you should preferably take the license or copying
> file from the package's tarball. (Make sure that it's utf-8 encoded.)
>
>> and who adds it to license_groups?
>
> Please wait for a another few days if anybody will raise objections,
> then you can add it yourself.
>
> Ulrich
>
Well, they updated their OFL version of fonts, so license is not
needed now :) Anyway, thanks for help.
prev parent reply other threads:[~2012-04-25 15:37 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
2012-04-25 9:58 ` Maxim Koltsov
2012-04-25 11:47 ` Ulrich Mueller
2012-04-25 15:36 ` Maxim Koltsov [this message]
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=CAB_Kkxy3O+eMPT9xM_L3PJabuFPGHHUqBw7aGooyXR0Zyq+jQg@mail.gmail.com \
--to=maksbotan@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