all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: 51046-done@debbugs.gnu.org
Subject: bug#51046: Close
Date: Fri, 8 Mar 2024 10:43:44 +0100	[thread overview]
Message-ID: <Zerd0Ld6c7xoQmPY@jurong> (raw)
In-Reply-To: <SUBY-hDCsK2thC0eX2cx2RQm84xwhff1uJL3k4YeoCYQLCyH-fzBm4vjIK_NW9x4_tvYoLRjm1b6XlbF1wY5yxe536ffvRJCTYvZNi7pKp0=@protonmail.com>

Thanks, phodina, for the patch, and Juliana, for undigging and
reviewing it! Given that the package looks unmaintained, I was a bit
hesitant, but since it still builds, why not add it; I took the liberty
to not wait for QA to build it out.

Before pushing, I changed the licence to gpl2+. Indeed, if later versions
are not explicitly excluded ("v2 only"), the GPL itself contains a clause
that implies "or later":

9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number.  If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation.  If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

Here it is also explicitly given in the source,
for instance there:
   https://github.com/njh/rdate/blob/main/src/rdate.c

Andreas





      parent reply	other threads:[~2024-03-08  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 22:45 [bug#51046] [PATCH] gnu: Add rdate phodina via Guix-patches via
2024-03-07 19:43 ` [bug#51046] [PATCH v2] " Juliana Sims via Guix-patches via
2024-03-08  9:43 ` Andreas Enge [this message]

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=Zerd0Ld6c7xoQmPY@jurong \
    --to=andreas@enge.fr \
    --cc=51046-done@debbugs.gnu.org \
    /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.