This is a *runtime* dependency, not an install-time one.
Basically, an extension can do this:
extension_config do |config|
config.extension "paperclipped"
end
The initializer will check that "paperclipped" is available in the app
and error out if not.
Sean
john muhl wrote:
On Sat, Sep 5, 2009 at 10:12 AM, Sean Cribbs <seancri...@gmail.com> wrote:
Looks like it's time for another release of Radiant:
WHAT'S NEW IN THIS RELEASE?
* Allow extensions to declare dependencies [Josh French]
does this mean that i can safely rip out all the code in ray that
tries to allow some extension dependencies? my feeling is that it
wasn't ever a hit feature in ray and that the implementation in
radiant is more usable/flexible.
is anyone using the dependency feature in ray who be sad to see it go?
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
