-
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
Make dependency on rugged optional #66
Comments
@sschuberth makes perfect sense. Any interest in submitting a pull request to do just that? |
@benbalter Interest yes, although I do not yet know how to technically do that, nor do I know when I would have some time. So if you have a clear idea how to implement it, please go ahead and do so. Otherwise I'll play around when I find some time. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@benbalter @sschuberth any idea how to deal with this? If it's quick I'd be glad to submit a PR. The dependency on rugged is making it very difficult for me to install this project. I should note I'm not a Ruby expert so I might need a few pointers for things that could seem basic. I can use Ruby but I'm much more versed in Node.js. |
Ok, in my particular case I was able to successfully install licensee in my system after installing the |
Another thing that would help here is to talk the rugged people into publishing pre-built binary gems for rugged. |
Now that there is support for filesystem-based projects, how about making the dependency on rugged optional, and only use it if it's already installed? The main reason for this being that rugged, as a native extension, can be a pain to install on some platforms, and after all a Git working tree can also be scanned by the filesystem scanner.
The text was updated successfully, but these errors were encountered: