Amar Takhar commented on a discussion: https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/issues/9#note_137705 Thanks, lots of great detail here, something I forgot to add is that the GUI only works off of Git repositories so a version is either a `git hash`, `tag`, or a `branch`. There will not be any downloadable versions the users specifies what they want and the default will always be `main`. A version of the GUI put into a release can have it's default version set to the release tag. I'm not sure what the solution is as it has to be worked into rtems-deployment somehow. Previous, historical versions can be kept in rtems-deployment as static `json` files though? These are not dynamic and would never change. Hosting them online somewhere does not make sense as once they are generated that's it for the life of the project. I can go back and generate those so we know for what release version of RTEMS which BSPs and architectures are available. As for main, I don't know I guess I'm stuck now forever checking out RTEMS which is what I really wanted to avoid doing. This means both rtems-deployment and the RSB will have to use that specific checked out repository so we're not constantly checking out copies of the RTEMS git repository for every action. Is it possible to tell both to only use the locally checked out version of RTEMS? -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/issues/9#note_137705 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
