Proper way to indicate dependencies?

I’m writing an engine for reuse that requires some other plugins -
what’s the right way to indicate those dependencies? Obviously, since
there’s no vendor directory under the engine, that code can’t be
bundled with the engine itself.

Thanks!


- Adam

** Expert Technical Project and Business Management
**** System Performance Analysis and Architecture
****** [ http://www.adamfields.com ]

[ http://www.aquick.org/blog ] … Blog
[ http://www.adamfields.com/resume.html ]… Experience
[ http://www.flickr.com/photos/fields ] … Photos
[ http://www.aquicki.com/wiki ]…Wiki

The simplest way is just to check/install those plugins when
installing the engine - see the install.rb in the login engine for an
example.

Adding the information to the README is also a great idea.

  • james

I seen a pretty cool hook in one of the engines I installed…

Create an install.rb file that contains something like the following.

Install the engines plugin if it has been already

unless File.exist?(File.dirname(FILE) + “/…/engines”)
Commands::Plugin.parse!([‘install’,
http://svn.rails-engines.org/plugins/engines’])
end

-NSHB

On 9/24/06, James A. [email protected] wrote:

what’s the right way to indicate those dependencies? Obviously, since
****** [ http://www.adamfields.com ]

  • J *
    ~

engine-users mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org


Nathaniel Steven Henry Brown

Open Source Insight - http://nshb.net
Open Source Development - http://inimit.com
Open Source Training - http://osevents.com

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs