On 4/12/19 5:58 pm, Sebastian Huber wrote: > On 04/12/2019 04:25, Chris Johns wrote: >> On 3/12/19 5:01 pm, Sebastian Huber wrote: >>> On 03/12/2019 00:06, Chris Johns wrote: >>>>> The first use of Doorstop is done in the new build system. I will update >>>>> the >>>>> documentation to mention this Doorstop release. I will use it to generate >>>>> the >>>>> fingerprints of the items. >>>> Do we need to capture Doorstop in our future releases? If so how? We have a >>>> requirement our release capture all source code so insulate ourselves >>>> against an >>>> upstream side not existing or restructuring. >>> On pypi.org you can download packages: >>> >>> https://pypi.org/project/doorstop/2.0.post2/#files >>> >>> Should we add a Git mirror to RTEMS? >> Does this help? I can capture a specific version somehow I suppose, ie from >> github. > > If you trust in the long-term availability of external services, you can also > do a: > > pip install doorstop==2.0.post2 > > Probably together with a virtualenv: > > https://packaging.python.org/guides/installing-using-pip-and-virtual-environments/
I have no real feel for what would work. It would be a guess now and then we find out later. >>> For what would we need Doorstop after a release? You need it after changes >>> in >>> specification files to update the fingerprints (e.g. fix of a typo in a >>> documentation file). In the worst case you could do this also by hand or >>> just >>> don't update the fingerprint. >> This is reasonable, I suppose. What about a user picking up a certified >> version >> of RTEMS years later and wanting to make some changes and Doorstop is now >> version 6 and something things have change? Is the release source captured >> the >> source to use a release or is it the source to use and maintain a release? > > Maybe we should just document in the RTEMS Software Engineering manual which > Doorstop version should be used, hope for the best and rely on pypi.org, and > make a backup of the Doorstop package of the specified version? Sure. Can the required version be a requirement, ie a YAML file? :) Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
