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

Don't require linguist/repository #1600

Closed

Conversation

calebhearth
Copy link

linguist/repository depends on the Rugged gem, which isn't included in the
github-linguist dependencies.

Applications and libraries using linguist/repository can still use it by
manually calling require 'linguist/repository'

This is option 1. Opening a parallel pull request to add a Rugged dependency.

This is my preferred approach since it doesn't add a new dependency, but
strictly speaking it also means that we need to bump the major version since
Linguist::Repository is no longer defined.

The reason for this change is that a 3rd-party with "require 'linguist'" gets a
load error for Rugged being missing since it is required in linguist/repository.

linguist/repository depends on the Rugged gem, which isn't included in
the github-linguist dependencies.

Applications and libraries using linguist/repository can still use it by
manually calling `require 'linguist/repository'`
calebhearth added a commit to calebhearth/html-pipeline that referenced this pull request Oct 16, 2014
Currently this also catches a LoadError for rugged, a dependency
Linguist added but didn't add to its gemspec.

github-linguist/linguist#1600
github-linguist/linguist#1601
@arfon
Copy link
Contributor

arfon commented Oct 16, 2014

Thanks for these @calebthompson - definitely favour #1601over this. I'm just trying to figure out why we moved the rugged dependency out of the gemspec in the first place.

@arfon arfon closed this Oct 16, 2014
@calebhearth
Copy link
Author

:( okay.

@github-linguist github-linguist locked as resolved and limited conversation to collaborators Jun 18, 2024
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.

2 participants