[Bf-committers] Lack of license docs for external libs and fonts

[IRIE Shinsuke]

Hi,

Using the Debian's dep5 format looks good, but this is used for
describing the source tree, so there are some problems:

- In the release archives, locations of the data files (fonts etc.)
   described by "Files" fields may be different from the source tree
- External static libraries such as OpenCOLLADA cannot be described

Anyway, for reference, I attached debian/copyright file I'm using for
deb packages in my PPA.  Note that this file is still incomplete
because it doesn't include descriptions of the functions partially
copied from external projects such as glib.

IRIE Shinsuke

13/03/26, Campbell Barton wrote:
> On Mon, Mar 25, 2013 at 5:27 AM, IRIE Shinsuke <irieshinsuke at yahoo.co.jp> wrote:
>> Hi,
>>
>> Currently, Blender's release archives include license documents only
>> for Blender(GPLv2) and Python, while any license docs for external
>> libraries and fonts such as Bullet physics are not included.  I think
>> that violates the software licenses and the copyrights.
>>
>> The release archives should include a directory like "licenses" which
>> contains the license docs for the external libs/fonts.
>>
>> Thanks,
>>
>> --
>> IRIE Shinsuke
>
> As well as there being external projects who's licenses we might miss,
> there are functions in files which are copied from other open-source
> projects.
> The ones I'm aware of have comments above the function stating its
> origin, but there isn't a good way to get an overview on who owns this
> copyright across many files.
>
> How about use the debian copyright format? (human and machine readable).
>
> http://www.debian.org/doc/manuals/maint-guide/dreq.en.html#copyright
> http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>