Feature/flexible release package location on relups #505
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now, when performing a relup using relx generate scripts, you need to take the tarball containing the relup of the next version and rename it to a specific filename (
<relname>.tar.gz
) which must be located in a specific location (releases/<version>
), when you generate a tarball the filename contains the version number so this renaming is inconvenient, this PR allows for a more flexible way:When running the unpack/install the upgrade install will search a set of locations and look for a tarball which meets the necessary criteria, it either contains the version number we're looking for or it conforms to the previous naming scheme for retro-compatibility, it then symlinks this tarball to one the release_handler is expecting (ie.
releases/<version>/<relname>.tar.gz
). The set of locations used to look for the user's tarball are (in order):releases/<relname>-<version>.tar.gz
releases/<version>/<relname>-<version>.tar.gz
releases/<version>/<relname>.tar.gz