From: Alex Kost <alezost@gmail.com>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: [gnu.org #954922] Vague "licensing" for the symbola font.
Date: Mon, 19 Jan 2015 22:39:18 +0300 [thread overview]
Message-ID: <87zj9eblw9.fsf@gmail.com> (raw)
In-Reply-To: <20150118155830.GA991@jocasta.intra> (John Darrington's message of "Sun, 18 Jan 2015 16:58:30 +0100")
John Darrington (2015-01-18 18:58 +0300) wrote:
[...]
> It could become a real issue, if, say, the author dies, his hiers then decide to
> make it into a proprietary software.
>
> I think Guix is right to take the cautious approach.
>
> (What actually depends on these fonts? There are oodles of fonts today. Can it
> be substituted by something else?)
Nothing depends on Symbola font, so it may be safely ignored. I just
use it all the time, so I proposed this package several months ago.
--
Alex
next prev parent reply other threads:[~2015-01-19 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 21:20 Fwd: [gnu.org #954922] Vague "licensing" for the symbola font Ian Denhardt
2015-01-16 20:37 ` Ludovic Courtès
2015-01-17 14:36 ` Alex Kost
2015-01-17 16:28 ` Ludovic Courtès
2015-01-18 14:04 ` Alex Kost
2015-01-18 14:23 ` Ludovic Courtès
2015-01-18 15:15 ` Jason Self
2015-01-18 15:58 ` John Darrington
2015-01-19 19:39 ` Alex Kost [this message]
[not found] <RT-Ticket-954922@rt.gnu.org>
2014-10-22 16:51 ` [PATCH] gnu: Add ttf-symbola Alex Kost
2014-10-23 6:26 ` Andreas Enge
2014-10-23 14:14 ` Eric Bavier
2014-10-24 6:52 ` Ian Denhardt
2014-11-13 20:15 ` Ludovic Courtès
2014-11-16 19:27 ` Ian Denhardt
2014-11-16 21:09 ` Ludovic Courtès
2014-11-19 3:28 ` [PATCH] gnu: Add ttf-symbola. [gnu.org #954922] Ian Denhardt
[not found] ` <rt-3.4.5-31938-1416367745-1484.954922-6-0@rt.gnu.org>
2014-12-16 21:58 ` [gnu.org #954922] Vague "licensing" for the symbola font Donald R Robertson III via RT
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zj9eblw9.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).