If I had a component to the registry and then want to remove it. What is the process to go about doing so?
Duplicate of #112
I can also cut it down, post it here and i'll do it
@satazor Can you add it to the readme how to go about removing a package? Maybe with a link to an ticket where they can just post the name of the package or something to be removed?
I accidentally added the "sinonjs" component before realizing that the package.json file in the repo is incompatible with bower. Instead, I created my own proxy repo where I provide the built sinon.js component and registered it in bower as "sinon.js". To avoid confusion, maybe remove the "sinonjs" component until the author fixes/provides support for bower.
Just a quick question, but if I do bower search sinon =>
bower search sinon
..and bower search sinon.js produces no results. If I bower install sinon I get a clone of the Sinon repo at https://github.com/cjohansen/Sinon.JS which requires a build step to produce a working client-side sinon.js file -- you can't use the source directly under lib w/o building first.
bower search sinon.js
bower install sinon
So, how can I use sinon via bower? Is there another built version in the repo somewhere?
Ok, this can be solved temporarily like this until someone creates a fork of the sinon repo that includes the built sinon.js library. The author of sinon.js (see thread linked) indicates he doesn't want to include the release library in his repo, so you may as well just delete the sinon bower project since it is not usable.
@davisford I created a proxy repo with the built file, but I was contacted by someone saying the repo was no longer necessary due to the official "sinon" registered in bower. I would be glad to recreate a proxy repository with the built file.
@blittle well if you do a bower install sinon it installs the official github url repo clone, which does not contain the built sinon.js library -- only the lib source before packaging. it is unusable (e.g. try to use sinon.stub() -- not there). The link i provided above provides some context -- author decided he doesn't want the pkg/ dir in there with the generated code, so your proxy probably is needed again -- or you can just reference the sinon release url directly in your bower file (that's what i do now). That's actually a little cleaner since I don't have to yank down a whole github repo just to use a library.
@davisford When I get a chance I'll recreate a proxy repo, it wasn't a fork of the actual sinon repo, rather a simple repo with just the files needed for deploy (and bower file too)