Skip to content
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

Make slackistrano optional #7

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Make slackistrano optional #7

wants to merge 3 commits into from

Conversation

gido
Copy link
Member

@gido gido commented Dec 7, 2020

💬 Describe the pull request

What if I don't want slackistrano ?

@gido gido requested a review from yannlugrin December 7, 2020 16:02
@@ -24,7 +24,6 @@ Gem::Specification.new do |spec|

spec.add_dependency 'capistrano', '~> 3.5'
spec.add_dependency 'capistrano-composer', '~> 0.0.6'
spec.add_dependency 'slackistrano', '~> 3.1'
Copy link
Member Author

Choose a reason for hiding this comment

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

I suppose this break BC but slackistrano should be optional

Copy link
Member

Choose a reason for hiding this comment

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

We could keep the gem dependency as that doesn't have so much effect. But if you want to remove it, why not.

Comment on lines 1 to 2
require 'capistrano/antistatique/httpauth'
require 'capistrano/antistatique/slackistrano'
require 'capistrano/antistatique/styleguide'
Copy link
Member

Choose a reason for hiding this comment

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

Maybe this file should be removed because even styleguide is optional.

Copy link
Member Author

Choose a reason for hiding this comment

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

I agree. But this will be a BC break, no?

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 a breaking change if you update the module on a project, but also an easy fix.

Copy link
Member

Choose a reason for hiding this comment

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

And that will probably not break the build, just stop to send notifications. Also, the dependency was removed from gemspec, so makes no sense to have this here.

Copy link
Member Author

Choose a reason for hiding this comment

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

OK, the Gemfile.lock works as expected (https://github.com/antistatique/cardis-server/blob/dev/Gemfile.lock#L2-L3)

Is the [0.1.0](https://github.com/antistatique/cardis-server/blob/dev/Gemfile#L7) doing something useful in the case of a reference to a git ?

Copy link
Member

Choose a reason for hiding this comment

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

No, it's useless

Copy link
Member

Choose a reason for hiding this comment

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

The only case that must be specified if not gem spec exist in the repository if I remember correctly

@@ -24,7 +24,6 @@ Gem::Specification.new do |spec|

spec.add_dependency 'capistrano', '~> 3.5'
spec.add_dependency 'capistrano-composer', '~> 0.0.6'
spec.add_dependency 'slackistrano', '~> 3.1'
Copy link
Member

Choose a reason for hiding this comment

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

We could keep the gem dependency as that doesn't have so much effect. But if you want to remove it, why not.

@yannlugrin
Copy link
Member

@gido About that, i think we should remove everything from lib/capistrano/antistatique.rb and let load what we need in each project. We could just print a message that tells the user to update the requirements in Capfile.

Do you agree with that?

@gido
Copy link
Member Author

gido commented Nov 24, 2021

@gido About that, i think we should remove everything from lib/capistrano/antistatique.rb and let load what we need in each project. We could just print a message that tells the user to update the requirements in Capfile.

Do you agree with that?

Yes. I'm in favor to cherry-pick for each project which recipes we need.

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

Successfully merging this pull request may close these issues.

2 participants