unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: 32916@debbugs.gnu.org
Subject: bug#32916: font-awesome v5 build scripts are not free
Date: Wed, 03 Oct 2018 15:33:12 -0400	[thread overview]
Message-ID: <87ftxmltaf.fsf@netris.org> (raw)
In-Reply-To: <20181002191330.GA12909@jasmine.lan> (Leo Famulari's message of "Tue, 2 Oct 2018 15:13:30 -0400")

Hi Leo,

Leo Famulari <leo@famulari.name> writes:

> We have a package of font-awesome, currently at version 4.7.0.
>
> It's a very simple package, installing the files generated by upstream
> rather than trying to rebuild them.
>
> As of version 5, the tools used to build the generated files are not
> free:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902981
> https://github.com/FortAwesome/Font-Awesome/issues/13467
>
> Is this a problem for us under the FSDG? Quoting the FSDG [0]:
>
> ------
> “Information for practical use” includes software, documentation, fonts,
> and other data that has direct functional applications. It does not
> include artistic works that have an aesthetic (rather than functional)
> purpose, or statements of opinion or judgment.
>
> All information for practical use in a free distribution must be
> available in source form. (“Source” means the form of the information
> that is preferred for making changes to it.)
> ------
>
> Since we don't have the form of the fonts that is preferred for making
> changes to them, my interpretation is that we can't include font-awesome
> version 5.
>
> What do you think?
>
> [0]
> https://www.gnu.org/distros/free-system-distribution-guidelines.en.html

I agree that version 5 of font-awesome does not meet the requirements of
the FSDG, which states:

  A free system distribution should be self-hosting.  This means that
  you must be able to develop and build the system with tools that the
  system provides you.  As a result, a free system distribution cannot
  include free software that can only be built by using nonfree
  software.

Moreover, it is doubtful that it could even be considered free software,
since it is not clear how users can effectively modify the font without
access to its build system, which is both proprietary and secret.

FWIW, the GNU GPL v3 definition of "corresponding source" includes the
build system:

  The “Corresponding Source” for a work in object code form means all
  the source code needed to generate, install, and (for an executable
  work) run the object code and to modify the work, including scripts to
  control those activities.

Therefore, I think we should keep 'font-awesome' frozen at version 4.7,
with a comment explaining the situation, to prevent others from
accidentally upgrading it.

What do you think?

      Mark

  parent reply	other threads:[~2018-10-03 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02 19:13 bug#32916: font-awesome v5 build scripts are not free Leo Famulari
2018-10-03  9:27 ` Gábor Boskovits
2018-10-03 19:33 ` Mark H Weaver [this message]
2018-10-03 21:26   ` Ludovic Courtès
2018-10-04  0:28     ` Mark H Weaver
2018-10-04  9:19       ` Ludovic Courtès
2019-02-26  0:32         ` Leo Famulari

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=87ftxmltaf.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=32916@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).