This is a request to split up the repository into at least two repositories
rspec
rspec_core (loaded as svn_external or git submodule)
rspec_on_rails (loaded as svn_external or git submodule)
We could load the plugins the same way as before
ruby script/plugin install http://rspec.rubyforge.org/svn/trunk/rspec_core
ruby script/plugin install
http://rspec.rubyforge.org/svn/trunk/rspec_on_rails
but it would be easier to install from git using git submodules
using git and calling from RAILS_ROOT
git submodule add git//github.com/dchelimsky/rspec_on_rails.git
vendor/plugins/rspec_on_rails
git submodule add git//github.com/dchelimsky/rspec_core.git
vendor/plugins/rspec
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/rspec-users/attachments/20080318/902561ca/attachment.html
On Tue, Mar 18, 2008 at 8:41 PM, Dominic Sisneros <dsisnero at gmail.com> wrote:> This is a request to split up the repository into at least two repositoriesI forwarded this to http://rspec.lighthouseapp.com/projects/5645/tickets/347. Please make future feature requests there instead of this mailing list. Thanks, David> > rspec > rspec_core (loaded as svn_external or git submodule) > rspec_on_rails (loaded as svn_external or git submodule) > > We could load the plugins the same way as before > ruby script/plugin install http://rspec.rubyforge.org/svn/trunk/rspec_core > ruby script/plugin install > http://rspec.rubyforge.org/svn/trunk/rspec_on_rails > > but it would be easier to install from git using git submodules > > using git and calling from RAILS_ROOT > > > git submodule add git//github.com/dchelimsky/rspec_on_rails.git > vendor/plugins/rspec_on_rails > git submodule add git//github.com/dchelimsky/rspec_core.git > vendor/plugins/rspec > > > > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
On Tue, Mar 18, 2008 at 10:41 PM, Dominic Sisneros <dsisnero at gmail.com> wrote:> This is a request to split up the repository into at least two repositories > > rspec > rspec_core (loaded as svn_external or git submodule) > rspec_on_rails (loaded as svn_external or git submodule) > > We could load the plugins the same way as before > ruby script/plugin install http://rspec.rubyforge.org/svn/trunk/rspec_core > ruby script/plugin install > http://rspec.rubyforge.org/svn/trunk/rspec_on_rails > > but it would be easier to install from git using git submodules > > using git and calling from RAILS_ROOT > > > git submodule add git//github.com/dchelimsky/rspec_on_rails.git > vendor/plugins/rspec_on_rails > git submodule add git//github.com/dchelimsky/rspec_core.git > vendor/plugins/rspec ><non-constructive-comment> Wow, a short command line to type, putting that into my brain will push out of the stack my 3 years old memories... </non-constructive-comment> Wouldn''t be better submit some patches to Rails and make script/plugin Git-aware? -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams
rails/plugin is git aware already in trunk for cloning a git repository. However, you can only clone from the git repository root (the directory which contains the .git directory). You can''t clone from a subdirectory. That''s why the project needs to be split to install both rspec and rspec_on_rails in the vendor/plugins directory using git. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20080318/52cba60e/attachment.html