Extract and extend license and copyright

[giulio93]

Please check if the PR fulfills these requirements

See how to contribute

• The PR has no duplicates (please search among the Pull Requests
  before creating one)
• The PR follows
  our contributing guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• UPGRADING.md has been updated with a migration guide (for breaking changes)
• configuration.schema.json updated if new parameters are added.

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change, and is titled accordingly?

Other information

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

The latest Buf updates on your PR. Results from workflow Check Protocol Buffers / check (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Jul 25, 2025, 1:18 PM

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.21%. Comparing base (cba02e8) to head (3140dd5).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2959      +/-   ##
==========================================
- Coverage   68.22%   68.21%   -0.02%     
==========================================
  Files         241      241              
  Lines       22696    22696              
==========================================
- Hits        15484    15481       -3     
- Misses       6012     6014       +2     
- Partials     1200     1201       +1     

Flag	Coverage Δ
unit	68.21% <ø> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[lucarin91]

I don't think this autogeneration system will be useful. I would just commit a copyright notice file without the env variable and use that during the build.

Suggested change

	append-license:
	desc: Render and append arduino-cli license to NOTICE file
	cmds:
	- |
	rendered=$(envsubst < .licenses/templates/arduino-cli-license.txt)
	notice_file=".licenses/NOTICE.arduino-cli"
	tmp_file=$(mktemp)
	echo "$rendered" > "$tmp_file"
	echo -e "\n" >> "$tmp_file"
	cat "$notice_file" >> "$tmp_file"
	mv "$tmp_file" "$notice_file"
	env:
	Year: '{{ now | date "2006" }}'
	Holder: "ARDUINO SA (http://www.arduino.cc/)"
	silent: false

[lucarin91]

Can you remove the comments and move to another directory? I think the root directory is ok. I would also remove the env variables and just create a file with the copyright notice all filled up.

[lucarin91]

Suggested change

	- cat /Users/sedia/repo/arduino-cli/.licenses/NOTICE.arduino-cli >> debian/arduino-cli/usr/share/doc/arduino-cli/copyright
	- cat .licenses/NOTICE.arduino-cli >> debian/arduino-cli/usr/share/doc/arduino-cli/copyright

[lucarin91]

Suggested change

task append-license

[lucarin91]

I would call this task something like update-deb-copyright