Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

Review packaging bundling of gems js requirements recommends #1948

Merged

Conversation

jordimassaguerpla
Copy link
Member

Review of how we package (RPM) portus.

Add gems as sources
Autogenerate autoprovides for js files
Remove mariadb requirement
Add kubectl requirement

@mssola
Copy link
Collaborator

mssola commented Sep 3, 2018

Add kubectl requirement

What do you mean by this? I see nothing on this regard (as it should) 😕

@jordimassaguerpla
Copy link
Member Author

@mssola : 88f2395

@mssola
Copy link
Collaborator

mssola commented Sep 3, 2018

@jordimassaguerpla so you meant portusctl, not kubgectl 😉

mssola
mssola previously approved these changes Sep 3, 2018
@@ -18,6 +18,15 @@
%define branch __BRANCH__
%define portusdir /srv/Portus

%define fix_sheb() ( \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is that a %define and not just a sh function?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not? Is there a reason not to use a macro?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's easier to read (no \ needed) and does not change behaviour depending on context.

Copy link

@MaximilianMeister MaximilianMeister left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

overall LGTM, i am only not sure if it would be better to %define rb_suffix before %define fix_sheb() where it gets used

@jordimassaguerpla
Copy link
Member Author

@MaximilianMeister : good catch. I added a commit defining fix_sheb after

Let's include the gems as sources instead of build requirements so
building this package does not require so many gem packages.

Build requiring rubygem packages is a "nightmare" when you try to build
portus in different repos:

* sometimes the rubygem RPMs are not there and need to be submited
* othertimes they are present but have a different version and that
 creates a conflict

Since the new macros in ruby-common are generating the

"Provides: bundled(rubygem(foo)) = version"

we don't need the BR to explicetely tell which rubygems are in, plus the
"provides" is much more explicit.

Signed-off-by: Jordi Massaguer Pla <[email protected]>
portusctl is a separate package

Signed-off-by: Jordi Massaguer Pla <[email protected]>
This will create automatically the provides for the js libs

Signed-off-by: Jordi Massaguer Pla <[email protected]>
we don't recomment mariadb anymore in the RPM since the recommended way
is to use an external container

review some text in comments

Signed-off-by: Jordi Massaguer Pla <[email protected]>
@jordimassaguerpla jordimassaguerpla force-pushed the review_packaging_bundling_of_gems_js_requirements_recommends branch from 3d6b245 to 89566d7 Compare September 3, 2018 15:08
@jordimassaguerpla jordimassaguerpla force-pushed the review_packaging_bundling_of_gems_js_requirements_recommends branch from eaf426d to e350e0c Compare September 3, 2018 15:11
@mssola mssola merged commit b6bb9db into master Sep 4, 2018
@mssola mssola deleted the review_packaging_bundling_of_gems_js_requirements_recommends branch September 4, 2018 06:42
@mssola
Copy link
Collaborator

mssola commented Sep 4, 2018

Thanks @jordimassaguerpla! 👏

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants