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

Bug#833187: RFS: yuma123/2.8-1 [ITP] -- netconf/YANG toolchain



 ❦  7 août 2016 16:40 CEST, Vladimir Vassilev <vladimir@transpacket.com> :

>>> That is correct they are only initial templates that have been
>>> generated by yangdump (mib2c equivalent tool) a long time ago and
>>> maintained manually afterwards. Only
>>> ./netconf/src/agt/agt_yuma_arp.{c,h}
>>> ./netconf/src/agt/agt_time_filter.{c,h}. No problem there.
>> You may want to add a specific comment in debian/copyright for
>> that. Something like that:
>>
>> Files: ...
>> Copyright: ...
>> License: ...
>> Comment:
>>   The skeleton of those files were generated by the yangdump tool which
>>   generates the boilerplate to build new modules. They are now maintained
>>   manually and constitute the preferred form of modification.
> IMO there is no problem here since the particular YANG models
> (yuma-arp.yang yuma-time-filter.yang) used to generate the initial
> templates are part of the Yuma project and licensed under the same BSD
> copyright as the rest of the project code. This is not the case where
> one of the removed IETF MIBs was used to generate the template. Do you
> agree with that?

It is not a copyright problem, it is a problem that the DFSG mandates
the build of everything from the preferred form of modification. Without
the comment, the package could be rejected on the ground that those
files are marked as generated. A note in the debian/copyright will save
you the time to explain it is not the case.

As for the ones that were generated from IETF MIB, if they are in the
same case, it is believed that API cannot be copyrighted. They could
therefore be licensed with the BSD license as well. Only the MIB
themselves must be removed. But this could be more debatable. Your pick.
-- 
Debian package sponsoring guidelines:
 https://vincent.bernat.im/en/debian-package-sponsoring.html

Attachment: signature.asc
Description: PGP signature


Reply to: