From: Christoph Erhardt <fedora@sicherha.de>
To: linux-man@vger.kernel.org
Subject: Is man-pages-posix redistributable?
Date: Mon, 29 Aug 2022 08:14:22 +0200 [thread overview]
Message-ID: <3765026.aeNJFYEL58@delle> (raw)
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
Hi list,
I have a question regarding the redistribution of man-pages-posix.
Prior to the 2017-a release, the POSIX_COPYRIGHT file contained the following
paragraph:
> Redistribution of this material is permitted so long as this notice and
> the corresponding notices within each POSIX manual page are retained on
> any distribution, and the nroff source is included. Modifications to
> the text are permitted so long as any conflicts with the standard
> are clearly marked as such in the text.
In the 2017-a release, that paragraph has disappeared. I would like to clarify
the implications of that for downstream distributions.
The Fedora project, which is known to be very strict about licensing concerns,
sees the new licence as impermissible and has dropped the POSIX man pages as a
consequence: https://bugzilla.redhat.com/show_bug.cgi?id=2116859
Now, Fedora's quasi-official way of dealing with such licensing issues would
be to add the item in question to RPM Fusion's 'nonfree' package repository. I
have opened an inclusion request:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6396
However, the discussion there has raised the question whether the contents of
man-pages-posix are redistributable *at all* - given that the clause
mentioning redistribution has vanished from the licence.
Could someone please clarify?
Thanks a lot,
Christoph
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-08-29 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 6:14 Christoph Erhardt [this message]
2022-09-18 14:51 ` Is man-pages-posix redistributable? Christoph Erhardt
2022-09-28 8:15 ` Christoph Erhardt
2022-09-28 13:56 ` Alejandro Colomar
2022-09-29 7:18 ` Christoph Erhardt
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=3765026.aeNJFYEL58@delle \
--to=fedora@sicherha.de \
--cc=linux-man@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox