[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: syntax-error-in-dep5-copyright syntax error in section 4 after the tag license



Hi Charles and Jan Pascal,

Thanks for your help. Your tips on 'space dots' got me on the right
track. I also had to include the plain text of an identical BSD
license twice, because it appeared in two different sections of my
copyright file.

Best wishes,

Guido

On Wed, Oct 12, 2011 at 8:17 AM, Jan-Pascal van Best
<janpascal@vanbest.org> wrote:
> Hoi Guido,
>
> This hit me also and it took some time to figure out.
> - indent multi-line fields with a space
> - use 'space dot' - ' .' for empty lines in a multi-line field.
>
> Like this:
>
> License: BSD-3-clause~FIZSH
>  Redistribution and use in source and binary forms, with or without
>  modification, are permitted provided that the following conditions are
>  met:
>  .
>      * Redistributions of source code must retain the above copyright
>        notice, this list of conditions and the following disclaimer.
>      * Redistributions in binary form must reproduce the above
>        copyright notice, this list of conditions and the following disclaimer
>        in the documentation and/or other materials provided with the
>        distribution.
>      * Neither the name of FIZSH nor the names of its contributors may
>        be used to endorse or promote products derived from this software
>        without specific prior written permission.
>  .
>  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>  "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>  LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
>  A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
>  OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
>  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
>  LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
>  DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
>  THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
>  (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
>  OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>
> Cheers
>
> Jan-Pascal
>
>
>
>


Reply to: