Page MenuHomeFreeBSD

Add ctfdiff
Needs ReviewPublic

Authored by aokblast on Dec 25 2024, 1:29 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Mar 9, 12:34 PM
Unknown Object (File)
Fri, Mar 7, 11:29 AM
Unknown Object (File)
Feb 9 2025, 6:41 PM
Unknown Object (File)
Feb 8 2025, 9:57 PM
Unknown Object (File)
Feb 8 2025, 5:43 AM
Unknown Object (File)
Feb 5 2025, 1:29 AM
Unknown Object (File)
Feb 4 2025, 6:33 AM
Unknown Object (File)
Feb 4 2025, 5:06 AM
Subscribers

Details

Summary

Wiki Page on introducing how to use this tool: https://wiki.freebsd.org/ShengYiHong/ABIStability

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 61330
Build 58214: arc lint + arc unit

Event Timeline

Remove unused CTF in Makefile

The elf parse, ctf parser is all from ctfdump and refactor it into C++. However, because it is cddl licensed, I am wondering if there is any legal concern?

usr.bin/ctfdiff/ctfdiff.1
7

Should the copyright header be yours?

The elf parse, ctf parser is all from ctfdump and refactor it into C++. However, because it is cddl licensed, I am wondering if there is any legal concern?

So not only included the CDDL headers but also some code derived from CDDL files?

cc @imp

The elf parse, ctf parser is all from ctfdump and refactor it into C++. However, because it is cddl licensed, I am wondering if there is any legal concern?

So not only included the CDDL headers but also some code derived from CDDL files?

cc @imp

Oh! I'm sorry, but this got lost in my inbox... I've been super busy...

So, it's hard to say. At the very least ctftype.cc needs some kind of acknowledgement that the code was derived from the original CDDL code.
The wrapping in C++ coupled with refactoring suggests that it may have reached the threshold to be a new, transformative work. However, since we're
linking with other CDDL code, I'd err on the side of considering it merely a derived work. This would mean labeling with CDDL and possibly moving
this utility to the cddl subtree.

The files generally need a copyright statement, so I'd start with where you got the elf parser from for those files that contain it (ctftypes.cc and ctfdata.cc
if my eye is right). I'd then add your copyright to that, and add the copyright + license statement to each of the other files. I suspect they should be CDDL
for simplicity, but BSDL 2-Clause is also a viable option.