# Script/plugin and polluted(?) sources **URL:** \ **Category:** Rails\ **Created:** [January 22, 2009, 10:35pm UTC](https://www.ruby-forum.com/t/script-plugin-and-polluted-sources/158399 "2009-01-22T22:35:03Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![fritza](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/5f9b8f/32.png) [@fritza](https://www.ruby-forum.com/u/fritza)\ **Post date:** [January 22, 2009, 10:35pm UTC](https://www.ruby-forum.com/t/script-plugin-and-polluted-sources/158399/1 "2009-01-22T22:35:03Z")
I recently had trouble installing the ssl\_requirement plugin. script/plugin said it couldn’t find ssl\_requirement. I “solved” this by running “script/plugin discover” and accepting the addition of a bunch of other repositories. The script could then discover and install ssl\_requirement. BUT: It wasn’t the same version of ssl\_requirement that I’d installed (and worked well with) on other projects. The version I got, in SslRequirement::ensure\_proper\_protocol, made use of a module called UserSystem, which I didn’t have installed. My guess (am I right?) is that someone modified the plugin for his own use and then put it into a public repository. How can I set script/plugin so that it pulls in only generally-released versions of the plugins? ``` — F ```