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

[Chris Johns (@chris)]

Chris Johns commented on a discussion on wscript: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113826

 > +                ctx.fatal("Invalid VERSION revision: too many dots")
 > +            if "-" in vs[0]:
 > +                value = vs[0]
 > +                vs = value.split("-", 1)
 > +                version_label = vs[1]
 > +            version_minor = vs[0]
 > +            prefix = "/opt/rtems/" + version_major
 > +        except configparser.NoOptionError:
 > +            pass
 > +    if version_major is not None:
 > +        version["__RTEMS_MAJOR__"] = version_major
 > +    if version_minor is not None:
 > +        version["__RTEMS_MINOR__"] = version_minor
 > +    if version_label is not None:
 > +        version["RTEMS_RELEASE_VERSION_LABEL"] = version_label
 > +    # Checking minor insures major and minor are valid

It can be used when someone is deploying a release. It is documented here:

https://gitlab.rtems.org/rtems/docs/rtems-docs/-/blob/main/eng/release-process.rst?ref_type=heads&plain=1#L116

This looks like a bug. I will fix it.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113826
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/20241026/65a5684c/attachment-0001.htm>