On Fri, Mar 18, 2011 at 05:47:06PM -0400, Brad wrote:
> On 18/03/11 5:32 PM, Pascal Stumpf wrote:
> >On Fri, Mar 18, 2011 at 05:07:59PM -0400, Brad wrote:
> >>On 18/03/11 4:07 PM, Pascal Stumpf wrote:
> >>>+.for _f in AUTHORS ChangeLog README LICENSE
> >>>+  ${INSTALL_DATA} ${WRKSRC}/${_f} ${PREFIX}/share/doc/privoxy
> >>>+.endfor
> >>
> >>The README is probably Ok. The rest is pointless.
> >
> >LICENSE is required. AUTHORS gives proper credit to people. ChangeLog
> >contains some relevant information about changes in behaviour and
> >configuration.
> 
> No, it isn't. 
Yes, it is. Section 3 of the GPLv2:

  3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
[...]

... and Section 1 it refers to:

  1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.


So the license needs to be distributed in any case (and most ports do
so).

> The other files are fine for the distribution tarball
> but have essentially no relevance to the port/package. If the user
> *needs*
> to know anything which requires changes upon upgrading mention it
> in the MESSAGE file or pkg README.
Some users may wish to be informed about changes that don't require
direct action for most setups. Additions to blocking rules, added
options, changes in logging behaviour etc.

> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> 

Reply via email to