RTEMS | waf: Fix handling of the VERSION file in a release (!257)
Sebastian Huber (@sebhub)
gitlab at rtems.org
Tue Oct 22 01:13:39 UTC 2024
Sebastian Huber commented on a discussion on wscript: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113432
> + from waflib.Errors import WafError
> + release_label = "not-released"
> + try:
> + modified = ctx.cmd_and_log("git ls-files --modified",
> + quiet=Context.BOTH).strip()
> + release_label = ctx.cmd_and_log("git rev-parse --short HEAD",
> + quiet=Context.BOTH).strip()
> + if len(modified) != 0:
> + release_label += "-modified"
> + except WafError:
> + pass
> + return release_label
> +
> +
> +#
> +# This class is not aligned the project's release labelling. It will
Is there any difference between `rtems_version_control_key()` and `rtems_version_release_label()` except the name?
--
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113432
You're receiving this email because of your account on gitlab.rtems.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20241022/949052aa/attachment-0001.htm>
More information about the bugs
mailing list