-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rename relocatable packages #10891
rename relocatable packages #10891
Conversation
Note that this PR requires to merge following submodule PRs before merging: |
f9d8619
to
00c8ca6
Compare
CI state |
CI state |
@avikivity ping |
This will break the release engineering pipeline, if it expects the old names. |
Well, it keeps older names by "-compat" target. |
@syuu1228 @avikivity Let me verify it before merging , i will prepare a PR to align pkg side |
@syuu1228 Can you please try to build it using https://jenkins.scylladb.com/view/master/job/scylla-master/job/byo/job/byo_build_tests_dtest/ ? |
We tried to build it on byo but it failed at strange error while building AMI, probably unrelated with this PR:
Since it's probably not a bug of this patch, I relaunched the jenkins job: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@syuu1228 Looks like pkg side is good to go, tested this on byo
centos
and unified-deb
gce' 'azure' and 'ami
all passed
LGTM
Currently, we use following naming convention for relocatable package filename: ${package_name}-${arch}-package-${version}.${release}.tar.gz But this is very different with Linux standard packaging system such as .rpm and .deb. Let's align the convention to .rpm style, so new convention should be: ${package_name}-${version}-${release}.${arch}.tar.gz Closes scylladb#9799
00c8ca6
to
e9dfa18
Compare
Rebased with latest master, since configure.py was conflicted with pip symlinks change. |
As I described on above, when we merge this please merge submodule PRs first, otherwise we will get build error. |
CI state |
Is releng ready for this? If I merge all the relevant patches, will everything work, or is something else needed from releng? |
@avikivity It will work.. |
Currently, we use following naming convention for relocatable package filename: ${package_name}-${arch}-package-${version}.${release}.tar.gz But this is very different with Linux standard packaging system such as .rpm and .deb. Let's align the convention to .rpm style, so new convention should be: ${package_name}-${version}-${release}.${arch}.tar.gz Closes #9799 Closes #10891
Currently, we use following naming convention for relocatable package
filename:
${package_name}-${arch}-package-${version}.${release}.tar.gz
But this is very different with Linux standard packaging system such as
.rpm and .deb.
Let's align the convention to .rpm style, so new convention should be:
${package_name}-${version}-${release}.${arch}.tar.gz
Closes #9799