On Tue, Jun 9, 2009 at 5:59 AM, Jim Gay<[email protected]> wrote: > On Jun 9, 2009, at 6:51 AM, Jason Garber wrote: > >> My suggestions for requirements: >> 1.) Extension authors have a way of specifying a minimum Radiant version >> with each release/revision of the extension. > > I chatted with John Muhl about this and I believe he implemented a > minimum/maximum Radiant version requirement in Ray ( in addition to the way > it handles dependencies).
yep, in a dependency.yml file use radiant_min_version and/or radiant_max_version, it's undocumented but there. currently it only works on your extension's extension dependencies since that was what Jim's use case called for, but there are plans to move it to the top level so you could apply the version constraints directly to the extension being installed, essentially making some version(s) of radiant a dependency for your extension. --- - extension: ext_name - radiant_min_version: 0.6.9 #current --- - radiant_max_version: 0.6.9 #future assuming extension authors start creating tags like 0.6.9, 0.7.0, 0.7.1 etc. i don't see why ray couldn't grab your radiant version and check for a tag that matches before just going after the latest version, i.e. master branch. >> 4.) The extension install script installs the latest compatible version of >> an extension. > > Definitely needed. Currently the registry only provides a compatible Radiant > version as an FYI and it's totally flat (only one version can be managed). any one know an extension that already uses tags like this? i'd like to get this working in ray. >> 5.) Easy upgrades. One command to upgrade Radiant and all my extensions. rake ray:extension:update name=all - it won't upgrade your radiant but any installed extensions would be > In addition, I think it would make complete sense to remove this page from > the wiki http://wiki.github.com/radiant/radiant/thirdparty-extensions i agree, just delete it, it's a relic from the pre-registry past and only adds confusion for new users and waste the time of anyone still listing their extension there. > Encouraging authors to put their content into the registry is long overdue. maybe script/generate extension NewExtension could encourage authors to add their extension to the registry. > I've been meaning to, but haven't had time, add a feature to the registry > where you can add an extension to the registry without an author (because > you might find an extension on github but the author hasn't signed up at the > registry), and later claim an orphaned extension as your own. anything that gets the extension list at the registry more complete sounds good to me. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
