I just checked the files in the GNU package
Many GNU packages fail to have copyright notices everywhere they should,
among failing other GNU policies, but that doesn't alter the
requirements. As you say, such are (minor) bugs in the packages.
I'm statistically certain that plenty of packages
Bob, Michael, John, Ineiev, anyone -
So, about getting ikiwiki installed, so the savannah documentation wiki
can be updated again and we can move forward.
Presumably it has to be installed on frontend, just as zope is now. Is
there a Debian package for ikiwiki under Debian 6[.0]? (Which is what
On 08/17/2013 08:50 AM, Eli Zaretskii wrote:
I.e. some kinds of generated files should have a notice.
Or just a pointer to the source, as the alternative above suggests.
Yes; the point is that those files include nothing like that.
> Date: Sat, 17 Aug 2013 08:22:04 +
> From: Ineiev
> CC: k...@freefriends.org, savannah-hackers-public@gnu.org
>
> On 08/17/2013 07:09 AM, Eli Zaretskii wrote:
> >> I unpacked a GCC distribution tarball and found no copyright notices
> >> in AUTHORS and ABOUT-NLS. probably it's a bug.
> >
>
Al 17/08/13 07:57, En/na Ineiev ha escrit:
I unpacked a GCC distribution tarball and found no copyright
notices in AUTHORS and ABOUT-NLS. probably it's a bug.
Even The Hurd itself doesn't contain a copyright notice in its configure.ac
http://git.savannah.gnu.org/cgit/hurd/hurd.git/tree/configure
On 08/17/2013 07:09 AM, Eli Zaretskii wrote:
I unpacked a GCC distribution tarball and found no copyright notices
in AUTHORS and ABOUT-NLS. probably it's a bug.
Unless these are generated files.
"When a file is automatically generated from some other file in the
distribution, it is useful for
> Date: Sat, 17 Aug 2013 05:57:13 +
> From: Ineiev
> Cc: savannah-hackers-public@gnu.org
>
> I unpacked a GCC distribution tarball and found no copyright notices
> in AUTHORS and ABOUT-NLS. probably it's a bug.
Unless these are generated files.
> Date: Fri, 16 Aug 2013 22:23:35 GMT
> From: k...@freefriends.org (Karl Berry)
>
> jll> if a README file contains a user manual, I think it should be
> licensed.
>
> Clearly that is true. But Ineiev is considering the typical case where
> the README is just a few lines of general inform
