<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
In my local development environment (MAMP) I do tend to use a lot of
symlinks. <br>
<br>
I also have one giant SVN repo which contains common modules that I
don't maintain (admin_menu, token, etc.) which can be symlinked in bulk.<br>
<br>
- Ken Winters<br>
<br>
Randy Fay wrote:
<blockquote
cite="mid:AANLkTinodvMZEWIYeZJjuIfwuD9tjNjAkcxQSDU0eatr@mail.gmail.com"
type="cite">Hi Ken - <br>
<br>
How do you build a dev site using your root-level contrib module
projects? Do you just symlink together a site?<br>
<br>
This is a classic Drupal problem, and it's not really even solved well
by git, which has submodule support, but not sure it makes everything
better.<br>
<br>
-Randy<br>
<br>
<div class="gmail_quote">On Sun, Jun 6, 2010 at 12:12 PM, Ken Winters
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:kwinters@coalmarch.com">kwinters@coalmarch.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I
use a single workspace for all my Drupal work (and a few other for code
using different<br>
coding standards).<br>
<br>
Then I do one "project" per module per active branch. For example, if
I need to implement<br>
a feature in D7 then backport to D6, I'll have one "project" per.
Importing a project via<br>
CVS makes this easy. Also, I can keep most of the projects closed and
cut down on memory footprint.<br>
<br>
I've also got one "project" per site, containing just code that is
unique to that site. Custom themes, etc.<br>
<br>
Long ago I had one mega-project with many CVS repos, but that was not
flexible and grew unwieldy.<br>
<font color="#888888"><br>
- Ken Winters</font>
<div>
<div class="h5"><br>
<br>
Syscrusher wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I need to be able to manage my modules for multiple Drupal core<br>
versions, and also for multiple modules, and I'm looking for advice from<br>
others as to the "best practices" for doing this. How did you partition<br>
your development environment as far as workspace, project, and folder<br>
levels, with regard to Drupal core and module versioning standards?<br>
<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Randy Fay<br>
Drupal Module and Site Development<br>
<a moz-do-not-send="true" href="mailto:randy@randyfay.com">randy@randyfay.com</a><br>
+1 970.462.7450<br>
<br>
</blockquote>
</body>
</html>