Henry Spencer's license
by Petr Šabata
While checking the contents of our `perl' package, I noticed the following:
/* NOTE: this is derived from Henry Spencer's regexp code, and should not
* confused with the original package (see point 3 below). Thanks, Henry!
/* Additional note: this code is very heavily munged from Henry's version
* in places. In some spots I've traded clarity for efficiency, so don't
* blame Henry for some of the lack of readability.
/* The names of the functions have been changed from regcomp and
* regexec to pregcomp and pregexec in order to avoid conflicts
* with the POSIX routines of the same names.
* pregcomp and pregexec -- regsub and regerror are not used in perl
* Copyright (c) 1986 by University of Toronto.
* Written by Henry Spencer. Not derived from licensed software.
* Permission is granted to anyone to use this software for any
* purpose on any computer system, and to redistribute it freely,
* subject to the following restrictions:
* 1. The author is not responsible for the consequences of use of
* this software, no matter how awful, even if they arise
* from defects in it.
* 2. The origin of this software must not be misrepresented, either
* by explicit claim or by omission.
* 3. Altered versions must be plainly marked as such, and must not
* be misrepresented as being the original software.
**** Alterations to Henry's code are...
**** Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
**** 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008
**** by Larry Wall and others
**** You may distribute under the terms of either the GNU General Public
**** License or the Artistic License, as specified in the README file.
You can see the whole file here:
I looked but couldn't find any common name for this license
of Henry's. Is it on our list? Is it free? What name should
I use in the License tag?
2 weeks, 3 days
allowed content in copr
by Zbigniew Jędrzejewski-Szmek
[This is a second posting, since the first seems to be stuck "in
moderation" for the last two days. Apologies if you get this twice.]
Please clarify what "violates any rules or guidelines of the Fedora
Project"  means.
My understanding that this does NOT mean all the Fedora Packaging
Guidelines and Update guidelines, since that would defeat the purpose
of copr to a large extent. In other words, I assume that packages
in copr cannot contain "bad" content, but it can be packaged in
arbitrary ways. The text can be read both ways.
This in context of discussion on fedora-devel .
As shown by that thread, people have contradictory explanations
so some clarification is needed.
My suggestion would be to strike point e. from the list.
4 years, 3 months