First of all: Thank you for this very nice piece of software! The possibilities and documentation are awesome.
I would like to run sdm in a GitHub Action, to have a customized pi image build automatically. This works already fine.
sdm is installed with the EZsdmInstaller script, which downloads always the most recent commit in the master branch:
|
[ "$SDMLAN" != "" ] && src=$SDMLAN || src="https://raw.githubusercontent.com/gitbls/sdm/master" |
This is a problem for me, because breaking changes like in sdm V8.x or new introduced bugs can break my build. This would not have to happen, as the build would continue to work fine using the old sdm version. To have a reliable auto build, I need to have the control when to update sdm, which means I need to be able to install a specific version of sdm. Another use case is testing something with a different version of sdm, for example to check for bugs.
Without any changes to sdm, I have this workaround:
- Download
EZsdmInstaller at a specific commit
- Replace
master in the download link with the id of the specific commit using for example sed
- Install
So the feature request is a clean way for installing a specific version. There are multiple ways to achieve this. For example, the installer script could have a parameter to specify a commit id replacing master. Adding tags to the release commits would even allow to specify a version instead of a commit id.
Please see this feature request just as something to start thinking, I don't see a high priority as I listed an easy workaround.
Thank you 😃
First of all: Thank you for this very nice piece of software! The possibilities and documentation are awesome.
I would like to run sdm in a GitHub Action, to have a customized pi image build automatically. This works already fine.
sdm is installed with the
EZsdmInstallerscript, which downloads always the most recent commit in the master branch:sdm/EZsdmInstaller
Line 60 in 210897b
This is a problem for me, because breaking changes like in sdm V8.x or new introduced bugs can break my build. This would not have to happen, as the build would continue to work fine using the old sdm version. To have a reliable auto build, I need to have the control when to update sdm, which means I need to be able to install a specific version of sdm. Another use case is testing something with a different version of sdm, for example to check for bugs.
Without any changes to sdm, I have this workaround:
EZsdmInstallerat a specific commitmasterin the download link with the id of the specific commit using for example sedSo the feature request is a clean way for installing a specific version. There are multiple ways to achieve this. For example, the installer script could have a parameter to specify a commit id replacing
master. Adding tags to the release commits would even allow to specify a version instead of a commit id.Please see this feature request just as something to start thinking, I don't see a high priority as I listed an easy workaround.
Thank you 😃