Shouldn't we just use rubygems? It already supports dependency management and versioning (this looks like the rails plugins vs gems discussion). We could version them with the radiant version so we could automate getting the proper version: - 0.7.1.2 (works on radiant 0.7.1) - 0.8.0.2 (works on radiant 0.8.0)
This would actually be my preferred solution, and I'd like to do some investigative work to see what (if any) modifications would need to be made to the extension architecture to support this.
I don't think it removes the need for a better set of community standards/guidelines for the development and management of extensions, though -- if anything, if you're going to maintain a product with actual concurrent releases you probably want a schema like the version- branches we've been discussion.
But to the point, I like where this is headed. There's another thread out there about using application templates to bootstrap a Radiant instance; that plus `config.gem 'radiant-awesome-extension'` could be some powerful mojo.
j _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
