On Mon, Jul 21, 2008 at 2:25 PM, john muhl <[EMAIL PROTECTED]> wrote:
> On 2008/07/21, at 10:39, Sean Cribbs wrote: >> >> In the case that the project is in git, you could manually create the >> .gitsubmodule file from the sha of the HEAD of the extension, since the >> submodules are just git repos themselves. I may support a switch in the >> script/extension installer for a scenario like this, but it will require >> some thought. >> > > Now I'm thinking that it might be simplest to just look for > RADIANT_ROOT/.git and if it's found switch into submodule mode, otherwise a > clone is done. > > My thinking is that if you have a .git directory at RADIANT_ROOT you've > either decided to scm your install or someone put it there for you because > they wanted to scm your install. In either case the best option is be a > submodule. I just passed over the Ray extension because I just saw "deploy with Capistrano" and thought "deploying with git is easy enough." But if it automatically installs extensions as git submodules, I'd be much more interested. Especially if the presence of a .git directory at the project's root automatically puts it in git mode. How easily does this fold into an existing Radiant install? Will it detect the submodules that are there already? -- Tim _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
