RTEMS | rtems-test needs a --version option or similar (#3671)

[Ayush Agarwal (@Ayush.ag)]

Ayush Agarwal started a new discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/3671#note_121813


The function _load_released_version() in rtemstoolkit/version.py calls a helper function (_load_released_version_config()) that searches for a version file in three potential locations: current dir as "VERSION", parent dir, and finally rtems-version.ini.

Thus, I can check if the user has provided the --version flag and load that version before the helper function is called.


saying that, I still am unable to figure out some major things-
1) which versions should be allowed by the user to switch from, is there any restrictions for that?
right now the string is split into a major version and a revision number plus the whole version stored as str. 
things get complicated when we allow the users to add their version. I can easily check for the proper format but what about a version(provided in proper format) which doesn't exist.

2)how would I test whether any implementation is actually changing the build version and working as intended. Which command should i run to check the code.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/3671#note_121813
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/20250326/90af65a0/attachment.htm>