Difference between revisions of "Building a roof over src"

From GlueXWiki
Jump to: navigation, search
(first draft)
 
m (Consequences?)
Line 13: Line 13:
 
  svn checkout https://halldsvn.jlab.org/trunk/sim-recon
 
  svn checkout https://halldsvn.jlab.org/trunk/sim-recon
  
making a directory "sim-recon" that contains a src directory.
+
making a directory "sim-recon" that contains a "src" directory.
  
 
===Advantages===
 
===Advantages===

Revision as of 11:38, 9 March 2010

What change is being proposed?

Move src to sim-recon/src

Consequences?

Instead of

svn checkout https://halldsvn.jlab.org/trunk/src

making a directory "src" in the local directory, we would do a

svn checkout https://halldsvn.jlab.org/trunk/sim-recon

making a directory "sim-recon" that contains a "src" directory.

Advantages

  1. everyone would have a directory with a standard name
  2. the tree itself would have a standard name, e. g. "first you check-out sim-recon"
  3. related: "src" is non-descriptive
    • every package in the known world has a "src" directory
    • there are other packages under trunk with descriptive names
  4. allows a more descriptive tag, e. g. sim-recon-2010-04-01
    • like root_5.25.02
  5. provides a natural home for "helper" directories, e. g., BMS, doc

Disadvantages?

  1. Not what we are used to; will cause some amount confusion.
  2. Work will have to be done.

Questions?

  1. If not now, then when?
  2. Should HALLD_HOME, HALLD_MY be renamed?

What about the name?

"sim-recon" is illustrative, could also be

  • halld (as in HALLD_HOME)
  • gluex
  • valparaiso
  • lawrenceville
  • newport-gnus
  • etc.