Use `ln -s` to create symlinks.�� They are compatible with both regular files, and directories (and other things like named pipes I believe).�� I would also recommend the git submodules (if you use Git).�� I have found it simpler to use Capistrano with submodules than to include all my projects in one big git repo (something that is easier to get away with in Subversion).
On Sat, Jul 25, 2009 at 2:38 PM, Chad Woolley <[address removed]>
On Sat, Jul 25, 2009 at 12:25 PM, brian schroeder <[address removed]> wrote:
You should take a look at git submodules. ��They are a little cumbersome but will likely satisfy your needs. ��Also, unlike svn, people tend to avoid having big git repositories that manage multiple projects. ��Each project typically has its own repository and is linked to others via submodules.
About piston:��if you want to modify your library in the context of one of your projects, there is no (easy) way to send the changes back to the library. ��This gets irritating fast.
Yes, learn Git submodules.�� They work fine in latest versions of git.�� There's no need for non-native solutions like braid/piston/etc anymore, unless you want to include subversion repos as subdirs.�� More and more tools (CI/IDE) are also offering git submodule support.�� The foreach option is the trick to easily managing multiple git submodules, make sure you learn it.�� Git submodules require you to learn and use a few different commands, but you can easily wrap these in rake tasks/scripts/aliases to fit your needs.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Chad Woolley ([address removed]) from The East Bay Ruby Meetup Group
To learn more about Chad Woolley, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here
Meetup Support: [address removed]
632 Broadway, New York, NY 10012 USA