unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon South <simon@simonsouth.net>
To: 44557@debbugs.gnu.org
Cc: Ekaitz Zarraga <ekaitz@elenq.tech>
Subject: [bug#44557] [PATCH] gnu: Add gputils.
Date: Tue, 10 Nov 2020 18:04:06 -0500	[thread overview]
Message-ID: <87eel0hl09.fsf@simonsouth.net> (raw)
In-Reply-To: <bxJ4DPtJrTnD8NTQWweobLco6VaTctkVeogiP1O-yfOXEwEGTnOwfVvyD0WMcDDxWUWaY_Z45_-HjX40CGXgx_bTHFXfg7n3knC-0Y1KrTk=@elenq.tech> (Ekaitz Zarraga's message of "Tue, 10 Nov 2020 20:23:13 +0000")

Ekaitz Zarraga <ekaitz@elenq.tech> writes:
> I packaged GPUtils...

I hate to jump in here with bad news, but I didn't expect anyone would
package gputils before I got around to sharing this:

While gputils itself is free software, I suspect some of the header
files contained in its distribution may not be, which makes the
licensing status of the project as a whole somewhat dubious. (This is
similar to the problem that affects SDCC[0].) I think gputils should be
reviewed carefully before the decision is made to include it in Guix.

As evidence, I submit the following:

- The "*.inc" files in gputils' "header" subfolder that are intended for
  use with PIC devices carry a copyright notice from Microchip[1], the
  current owner of the PIC design, but I have found no mention of any
  special terms for the files' distribution, nor any notice that they
  too have been released under the terms of the GPL.

- SDCC, a free C compiler for microcontrollers, distributes header files
  of its own that are also derived from files originally provided by
  Microchip. When they approached the company[2] in 2010 to verify they
  had permission to distribute their derivative versions under the GPL,
  Microchip responded[3] to say the files could be distributed but with
  the requirement they be used only with "authentic" PIC-compatible
  controllers produced by Microchip themselves. This violates freedom
  0[4], making the files non-free and (worse) any software compiled with
  SDCC that relies on these files non-free as well.

  Consequently, the SDCC project moved these files to a "non-free"
  section of their source tree and added build and run-time options to
  control their use.

Now here's where things get a little murky:

- The Microchip-copyrighted files from which the SDCC project derives
  their non-free header files are... the same Microchip-copyrighted
  files gputils provides in its "header" folder. This is clear from the
  SDCC manual[5] in section 4.7.10, "Adding New Devices to the Port",
  which gives instructions on converting gputils' supposedly free
  "*.inc" files into "non-free" header files for use with SDCC.

How is it, then, that these files can be distributed freely under the
GPL with gputils, while files produced from them cannot be freely
distributed with SDCC? I suspect the answer is that _neither_ project
has permission to distribute these files under a free license, and in
the case of gputils, no one has raised the question yet.

Obviously I feel we _should_ raise the question before deciding to
include gputils as a package in Guix. Unfortunately, it is looking to me
as though there may not be a place for PIC-compatible controllers,
Microchip-branded or otherwise, in the free-software world.

[0] https://issues.guix.gnu.org/44374
[1] See e.g.
    https://sourceforge.net/p/gputils/code/HEAD/tree/trunk/gputils/header/p10f200.inc
[2] https://sourceforge.net/p/sdcc/mailman/sdcc-devel/thread/4C508624.8000308%40siol.net/#msg25835011
[3] https://sourceforge.net/p/sdcc/mailman/sdcc-devel/thread/1DB7F50D3A07E6439E44C13B1A4470520D09F306%40CHN-CL-MAIL01.mchp-main.com/
[4] https://www.gnu.org/philosophy/free-sw.html
[5] http://sdcc.sourceforge.net/doc/sdccman.pdf

-- 
Simon South
simon@simonsouth.net




  reply	other threads:[~2020-11-10 23:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 20:23 [bug#44557] [PATCH] gnu: Add gputils Ekaitz Zarraga
2020-11-10 23:04 ` Simon South [this message]
2020-11-11 11:28   ` Ekaitz Zarraga
2020-11-29 22:36     ` Ludovic Courtès
2021-06-14  2:44       ` Maxim Cournoyer
2021-06-14  8:08         ` Ekaitz Zarraga
2021-06-25  4:04           ` Maxim Cournoyer

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=87eel0hl09.fsf@simonsouth.net \
    --to=simon@simonsouth.net \
    --cc=44557@debbugs.gnu.org \
    --cc=ekaitz@elenq.tech \
    /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).