RTEMS | waf: Fix handling of the VERSION file in a release (!257)

[Sebastian Huber (@sebhub)]

Sebastian Huber started a new discussion on wscript: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113386

 > +    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

It would be really great if this could be discussed first and then documented in the RTEMS Software Engineering manual. The `rtems_version_control_key()` is already present in the RTEMS 5 release.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113386
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/20241021/70fba381/attachment.htm>