User login

Agaric's new SVN repository layout to play well with contributing to CVS

Searched words: 
SVN repository for Drupal with CVS for contributing to Drupal

We need to keep track of our own modules.

Here's a plan:

  • Keep using trunk for development, with all the modules checked into it.
  • More importantly, use another directory for stable. We repeatedly tag/branch (same thing in SVN I think) out to stable, and stable can be directly checked out into an agaric directory within sites/all/modules.

Supposedly we can also check our modules in development directly to sites/specific/modules if we need to
use our modules before surely stable.

But then we can't check out our own modules from Drupal CVS.

Hrm.

I suppose we could remove modules from stable, and put them in a proper tag to check out into our import-to-CVS directory.

Or we can keep our regular contributed Drupal modules in modules/contributed instead of sites/all/modules. Hmm.

The goal is so we also have some modules that will never be contributed to Drupal.org (such as one we plan for promoting our own sites)

http://www.pushok.com/help/svnscc/index.php?redirect=adv_tagsbranches.htm
Installing subversion (not the instructions we followed, and whatever we did workedd, but this should work too)
http://hivelogic.com/narrative/articles/svn_on_os_x?status=301
http://svnbook.red-bean.com/

Resolution

Comments

Current thoughts-- we change

Current thoughts-- we change the current directory structure:

agaric-modules/example_agaric_module/5/example_agaric_module/example_agaric_module.module

to:

agaric-modules/5-dev/example_agaric_module/agaric_module
agaric-modules/5-stable/example_agaric_module/agaric_module

But that loses space for notes and everything. So maybe we can make branches of our modules from the current directory to an agaric-modules-stable/5/ directory that keeps them in a flat hierarchy.

And then we can check out and update 5-stable into our sites/all/modules directories as agaric-modules, to do check-outs and updates for all our in-house modules at once.

@TODO ben-agaric: research branching in SVN.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Syntax highlight code surrounded by the {syntaxhighlighter SPEC}...{/syntaxhighlighter} tags, where SPEC is a Syntaxhighlighter options string or "class="OPTIONS" title="the title".
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.