Calling all rails darcs users! We may be in the minority, but I''m sure we can still share some know how here. Question: how are you managing your vendor/rails directory? svn externals seems to be the preferred option for svn folk (at least this is the approach recommended in the Agile 2 beta). Is there a way to get the same functionality within darcs? That would seem to be the ideal solution. I''ve tried a few things: Check vendor/rails into darcs ---------- This makes things very easy, but do you really want all those files in your repository? Especially since with darcs it''s so easy to branch, and each branch is the entire repository. Link vendor/rails to a local svn checkout of rails ---------- svn co http://dev.rubyonrails.org/svn/rails/trunk /somewhere/rails ln -s /somewhere/rails (run in vendor) This works and means that at least you only need one copy of edge rails. However symbolic links are not supported by darcs, and you will have additional issues when deploying with capistrano (or otherwise). Please share your solutions or comments on the above. Thanks! -- Martyn
Calling all rails darcs users! We may be in the minority, but I''m sure we can still share some know how here. Question: how are you managing your vendor/rails directory? svn externals seems to be the preferred option for svn folk (at least this is the approach recommended in the Agile 2 beta). Is there a way to get the same functionality within darcs? That would seem to be the ideal solution. I''ve tried a few things: Check vendor/rails into darcs ---------- This makes things very easy, but do you really want all those files in your repository? Especially since with darcs it''s so easy to branch, and each branch is the entire repository. Link vendor/rails to a local svn checkout of rails ---------- svn co http://dev.rubyonrails.org/svn/rails/trunk /somewhere/rails ln -s /somewhere/rails (run in vendor) This works and means that at least you only need one copy of edge rails. However symbolic links are not supported by darcs, and you will have additional issues when deploying with capistrano (or otherwise). Please share your solutions or comments on the above. Thanks! -- Martyn
> This makes things very easy, but do you really want all those files in your repository? Especially since with darcs it''s so > easy to branch, and each branch is the entire repository.does it offer in-place branching or do you need to create another directory and/or repository?> Link vendor/rails to a local svn checkout of rails > ---------- > svn co http://dev.rubyonrails.org/svn/rails/trunk /somewhere/rails > ln -s /somewhere/rails (run in vendor) > This works and means that at least you only need one copy of edge rails. However symbolic links are not supported by darcs, > and you will have additional issues when deploying with capistrano (or otherwise). > > Please share your solutions or comments on the above.my solution was to switch to git. heres my .git/info/exclude: *\#* *.db *.sql log public/images tmp vendor and just symlink in markaby and rails trunk checkouts into vendor. if darcs doesnt understand symlinks maybe you can just ignore the vendor directory? does it support something similar to .git/hooks/update? then you can have it fetch svn-remote stylee.. to deploy, i git push a ''release'' branch over ssh to the server, and have a remote hook refresh mongrel_rail''s environment.. no swallows harmed..
Hello Martyn, 2006/8/15, Martyn Loughran <me@mloughran.com>:> Question: how are you managing your vendor/rails directory?I liked what I saw of Darcs. I have not switched, nor do I know if I will. The way I would have done it is to really have a copy of Rails in the application. That way, I could do local changes to Rails (apply patches, etc) that would only impact this application. I had built myself a script which updated a working copy of Rails, and checked it in to a Darcs repository. Then I used this repository as the base for the next repository. I had a hierarchy of Darcs repositories: Rails Edge | v Rails + Patches | v Application (vendor/rails) Then, any application I wanted to use could get the vanilla version of Rails, or a patched one. Plus, I could add local patches too. Thanks, and have a nice day ! -- Fran?ois Beausoleil http://blog.teksol.info/