all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 26588@debbugs.gnu.org
Subject: bug#26588: [PATCH 1/3] licenses: Add Bitstream Vera.
Date: Mon, 01 May 2017 13:00:47 +0200	[thread overview]
Message-ID: <87a86wdeow.fsf@lassieur.org> (raw)
In-Reply-To: <87bmrfb9f9.fsf@fastmail.com>

Marius Bakke <mbakke@fastmail.com> writes:

> Clément Lassieur <clement@lassieur.org> writes:
>
>> Marius Bakke <mbakke@fastmail.com> writes:
>>
>>> Hello! Thanks for bringing this up.
>>>
>>> Clément Lassieur <clement@lassieur.org> writes:
>>>
>>>> * guix/licenses.scm (bitstream-vera): New variable.
>>>
>>> [...]
>>>   
>>>> +(define bitstream-vera
>>>> +  (license "Bitstream Vera"
>>>> +           "https://www.gnome.org/fonts/#Final_Bitstream_Vera_Fonts"
>>>> +           "\"The Font Software may be sold as part of a larger software package
>>>> +but no copy of one or more of the Font Software typefaces may be sold by
>>>> +itself.\"
>>>> +
>>>> +The license is non-free because of the above clause, but a Guix package is a
>>>> +\"larger software package\"."))
>>>
>>> Instead of "officially recognizing" these licenses, which are unlikely
>>> to be re-used and ostensibly non-free, perhaps we could have a
>>> "fsdg-compatible" license procedure similar to "fsf-free". What do you
>>> think?
>>
>> Well, bitstream-vera is used twice (if we include 0ad).  But anyway
>> that's okay.  I should specify in the fsdg-compatible 'comment' argument
>> that it is non-free, right?  Or maybe all fsdg-compatible would be
>> non-free?
>
> 0ad could include (package-license font-bitstream-vera) instead. I also
> came across this font in "Hedgewars", so it's fairly prevalent.
>
> The default comment of the "fsdg-compatible" (or fsdg-free as Debian
> describes it[0]) license procedure should say something about not
> necessarily being free, but passing FSDG criteria; but it's good to have
> more specific comments in the actual packages.
>
> Anyway, just an opinion, but I think such a procedure would be nice to
> have :)
>
> [0] https://packages.debian.org/sid/ttf-bitstream-vera

Ok!  Here are two patches: one adds fsdg-compatible, and the other
updates the font package.  I'll also send the 0ad update to the 0ad
debbugs thread.

  reply	other threads:[~2017-05-01 11:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 14:46 bug#26588: Add some (non-free?) font licenses Clément Lassieur
2017-04-21 14:48 ` bug#26588: [PATCH 1/3] licenses: Add Bitstream Vera Clément Lassieur
2017-04-21 14:48   ` bug#26588: [PATCH 2/3] licenses: Add Arev Clément Lassieur
2017-04-21 14:48   ` bug#26588: [PATCH 3/3] gnu: font-bitstream-vera: Change license to Bitstream Vera Clément Lassieur
2017-04-21 15:30     ` Clément Lassieur
2017-04-26  9:13   ` bug#26588: [PATCH 1/3] licenses: Add " Marius Bakke
2017-04-29  9:57     ` Clément Lassieur
2017-04-29 14:00       ` Marius Bakke
2017-05-01 11:00         ` Clément Lassieur [this message]
2017-05-01 11:01           ` bug#26588: [PATCH 1/2] licenses: Add new meta-license fsdg-compatible Clément Lassieur
2017-05-01 11:01             ` bug#26588: [PATCH 2/2] gnu: font-bitstream-vera: Change license to fsdg-compatible Clément Lassieur
2017-05-01 14:53           ` bug#26588: [PATCH 1/3] licenses: Add Bitstream Vera Marius Bakke
2017-05-01 19:37             ` Clément Lassieur

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=87a86wdeow.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=26588@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.