mesonbuild / mesonbuild/wrapdb
license of wrap files and meson files
- Dominant language
- Meson
- Stars
- 118
- Forks
- 298
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 24
Description
In many cases wrap files are directly integrated into the repositories of various projects, however, they contain no SPDX license identifiers or similar. Manually adding them is not ideal because they are not preserved during updates. Specifying any kind of license using REUSE.toml, .dep5, etc. is possible, but it is a bit of work.
1. the repository mentions the MIT license, does that apply to all wrap and meson files?
2. would it be possible to inject an SPDX annotation into the wrap files (downloaded using `meson wrap install`)?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the repository's MIT licensing references and the REUSE.toml or .dep5 approaches mentioned in the issue. Then trace how files are downloaded by `meson wrap install`; a complete outcome would clarify the license coverage and determine whether SPDX annotations can be injected without being lost on updates.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100