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

Support forked repos of registered components #135

blittle opened this Issue Nov 13, 2012 · 2 comments


None yet
2 participants

blittle commented Nov 13, 2012

The registered component visualsearch has some compatibility issues with the newer versions of jquery. I forked their repo and fixed some of the problems (waiting on pull request).

In the mean time, I try to define visualsearch as my repo directly:

  dependencies: {
     "visualsearch": "git://"

The problem is that bower forces me to get the upstream version (which is registered as visualsearch in bower). This still happens even if I change the key from visualsearch to visualsearch-new. Should bower be automatically resolving and forcing me to use the upstream version?


This comment has been minimized.


satazor commented Nov 14, 2012

@blittle What version do you use?
If you got > 3, bower is hitting your repository, but is fetching the latest tag which does not have your fixes.
For now you have to release a new tag for bower to pull your changes.

See #107

@fat See what I mean? People always fall in this same error. If we could specify a branch + latest commit, and this was documented, this would not happen.


This comment has been minimized.

blittle commented Nov 14, 2012

@satazor I didn't realize that bower forced you onto a particular tag. I created a new tag 0.3.1 which for now resolves this particular issue. I agree that an option should exist to install the latest branch and commit. Also, this should be documented.

Thank you :)

@blittle blittle closed this Nov 14, 2012

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