Istvan,
I am totally for this. Some hurdles we'll have to overcome:
1) Numerous places where files in extensions use a relative path to find
config/environment.rb or other files in the gem. This is especially
relevant to running tests.
2) Resolving inter-extension dependencies so as to avoid the merb-style
dependency hell. The simple solution for this is to strongly suggest
that extensions use = version dependencies rather than =.
Sean
Istvan Hoka wrote:
Hi all!
This is a request for comments regarding the possibility of packaging
Radiant extensions as gems. I am addressing this mostly to those familiar
with Radiant internals. Others are welcome to contribute, of course.
Is it technically possible to load Radiant extesions as gems, in a manner
similar to the way Rails loads plugins from gems?
There are several reasons for wanting this:
1. Versioning. Packaging extensions as gems lets us leverage the gem
versioning mechanism. This way we would be able to state that Radiant
version 0.8 is compatible with a certain extension version 1.2.
2. Management. You could have several versions of the same extension
installed on your system, and various projects running different versions of
Radiant would just use the one specified. No git submodules or vendoring of
extensions needed. This ties into versioning.
I would be willing to invest the time in making this happen.
Is anyone else interested in seeing this?
I anyone interested in helping out?
Can anyone point me in a starting direction?
Thanks!
--
Istvan Hoka
___
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
