Personally, I think this is a great approach for files that already have
verbose license breakdown comments above the License tag. Such
breakdowns are technically no longer required[1], but I find they are
still a great help when maintaining or auditing packages with complex
licensing. I will probably give it this suggestion try the next time I
update one of those packages.
[1] https://gitlab.com/fedora/legal/fedora-legal-docs/-/issues/64
On 9/9/24 10:21 AM, Vít Ondruch wrote:
Dne 09. 09. 24 v 16:00 Miroslav Suchý napsal(a):
Dne 09. 09. 24 v 3:33 odp. Vít Ondruch napsal(a):
Neat. This would allow to slap in some comments, right? E.g:
~~~
License: %{shrink:
%dnl src/*.*
MIT AND
BSL-1.0 AND %dnl doc/*.*
BSD-2-Clause AND
(Apache-2.0 OR MIT OR BSL-1.0)
}
Technically yes, but please do not.
There is already
https://reuse.software/
that has structure, documentation, linters, libraries...
But that is upstream stuff, isn't it?
My idea is to replace blocks like:
~~~
# MIT: src/*.*
# BSL-1.0: doc/*.*
License: %{shrink:
MIT AND
BSL-1.0 AND
BSD-2-Clause AND
(Apache-2.0 OR MIT OR BSL-1.0)
}
~~~
which are hardly any better.
Somehow incorporating this would be great.
Don't disagree, but this is IMHO orthogonal to my proposal.
Vít
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
