all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon South <simon@simonsouth.net>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 54327@debbugs.gnu.org
Subject: [bug#54327] [PATCH 3/3] gnu: sdcc: Update to 4.2.0.
Date: Fri, 11 Mar 2022 04:17:32 -0500	[thread overview]
Message-ID: <87y21gu9ub.fsf@simonsouth.net> (raw)
In-Reply-To: <a739a0f87a1f61817e262c74d31d73270da03075.camel@telenet.be> (Maxime Devos's message of "Fri, 11 Mar 2022 08:40:21 +0100")

Maxime Devos <maximedevos@telenet.be> writes:
>> - See:
>> - 
>> + However: Many think that the Microchip requirement is not legally enforceable,
>> + arguing that the header files only contain noncopyrightable facts.
>
> This documentation change was not mentioned in the commit message.
> Could you give some context?

That text was added by the SDCC authors in the new version of the
software, not by me.  (This is a patch to an existing patch, so the
change here is actually to the text that surrounds the text being
modified.)

If you're asking for context on what the text refers to, it has to do
with header files bundled with SDCC that are provided under only a
restrictive license.  These are technically non-free and I'm attempting
to maintain a patch to SDCC that removes these files, the code that
enables their use, and instructions in the manual that encourage their
use (see https://issues.guix.gnu.org/44374).

As to the text itself, I didn't remove it because this didn't seem
necessary; I am trying to make as few changes as possible; and I am not
attempting to editorialize the SDCC documentation, merely to explain why
certain features are absent.

> To reduce the amount of patching required (and increase the
> robustness), perhaps only 'configure.ac' could be patched and
> 'autoreconf' could be run to regenerate 'configure'?

Yes, that's a better way of doing it.  I'll make this change with the
next update to the package.

-- 
Simon South
simon@simonsouth.net




  reply	other threads:[~2022-03-11  9:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 12:27 [bug#54327] [PATCH 0/3] gnu: sdcc: Update to 4.2.0 Simon South
2022-03-10 12:31 ` [bug#54327] [PATCH 1/3] gnu: sdcc: Remove input labels Simon South
2022-03-10 12:31 ` [bug#54327] [PATCH 2/3] gnu: sdcc: Build debugger with readline support Simon South
2022-03-10 12:31 ` [bug#54327] [PATCH 3/3] gnu: sdcc: Update to 4.2.0 Simon South
2022-03-11  7:40   ` Maxime Devos
2022-03-11  9:17     ` Simon South [this message]
2022-03-11 20:17       ` Maxime Devos
2022-03-11  7:42   ` Maxime Devos
2022-03-10 23:42 ` bug#54327: [PATCH 0/3] " Nicolas Goaziou

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=87y21gu9ub.fsf@simonsouth.net \
    --to=simon@simonsouth.net \
    --cc=54327@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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.