-
Notifications
You must be signed in to change notification settings - Fork 258
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
[RPM M3] RPM package requirements #1548
Comments
Need to set the package to not relocatable:
|
https://github.com/jordansissel/fpm/blob/master/templates/rpm.erb#L64-L66 Supply |
In research on testing remove the post_remove.sh and verify whether the dir are removed. |
Dependency runs:
|
|
|
Still need to find a better way to handle third party JDKs, as of now only bundled JDK run. |
some tests
|
20220218: PA issue block 1.3.0 build now. |
20220219: RPM core extracted + install zips + rpmbuild to repack with all the requirements:
Installation + Verification Logs
|
20220301: More issues debating whether make JDK a dependency a good idea, let alone nodejs is very hard to treat as a dependency due to node10 too old: #1682 & opensearch-project/OpenSearch#2302 |
Resolved by #1726 |
opensearch-1.2.0-linux-x64.rpm
for nowAfter talking to @spotaws I then manually remove
PREFIX
to set package to unlocatable. However, this requires--edit
and manually tweak file. Will need to get a fork of FPM and remove the default pending of PREFIX then send a PR.I find a workaround to provide "" to
--prefix
and now the package is not relocatable. Code in comments.20220209 Update: Able to get dependency requirements running in rpm spec file
20220301: More issues debating whether make JDK a dependency a good idea, let alone nodejs is very hard to treat as a dependency due to node10 too old: #1682 & opensearch-project/OpenSearch#2302
20220208 new issue: opensearch-project/OpenSearch#2073
Additional information:
release
to allow re-release of a package without changing the main version. (e.g. 1.2.4-1, 1.2.4-2, 1.2.4-3......) (Done)The text was updated successfully, but these errors were encountered: