On Thu, May 26, 2022 at 8:46 AM Miroslav Suchý <msuchy@xxxxxxxxxx> wrote:
Dne 25. 05. 22 v 14:40 Daniel P. Berrangé napsal(a):
> Ewwww, please no. Apps need to know whether a given RPM is using SPDX
> or not, independantly of whether they have Fedora git source history
> available. We just need to record this fact in the specfile explicitly,
> so it is available both to maintainers and to any apps parsing the
> spec and to any apps querying the installed RPMDB.
We can hardly avoid a transition period. So any application (and I am aware of just rpminspect and rpmlint) will know
that everything prior F35 and EPEL-7 use short names. And everything after F39 and EPEL 10 will use SPDX.
In the between we just need to somehow track what was migrated and what not. That can be bugzilla, special macro (which
likely should be removed after few years) or git log.
While functional, I don't like embedded spdx within the license tag. It's just ugly... But could we not have some sort of special tag/statement in the git log / %changelog that can be picked up programmatically?
That way it doesn't uglify the main part of the spec and will eventually be trimmed off.
Thanks,
Richard
_______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
