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

[RFC] How should we call out external dependencies? #105

Open
majormoses opened this issue Mar 6, 2018 · 0 comments
Open

[RFC] How should we call out external dependencies? #105

majormoses opened this issue Mar 6, 2018 · 0 comments

Comments

@majormoses
Copy link
Member

People are often confused when a particular plugin fails to install or run but it is unclear what is the missing dependency. These can range from a c compiler to client libs. I'd like to see that kind of information make their ways into the gemspec even if we can't auto install them we should call them out.

I think there are a couple approaches:

  • as the plugins have been having testing slowly rolled out to them I have been including a bootstrap.sh that installs various packages that are needed to run it
  • use gem metadata

I think requirements seems like a logical place to call these out in a uniform way. As this offers a better programmatic interface I think this makes the most sense but I am open to hear what others think.

I can think of several advantages of using the metadata for users and maintainers. For example if I wanted to query all the packages that require a compiler I could do that much easier through the rubygems api then parsing through some ad-hoc bootstrap scripts that may include other things like development/testing dependencies that are not needed for production.

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

No branches or pull requests

1 participant