Difference between revisions of "Building a roof over src"
From GlueXWiki
m (→Consequences?) |
m (→Advantages) |
||
(7 intermediate revisions by the same user not shown) | |||
Line 7: | Line 7: | ||
Instead of | Instead of | ||
− | svn checkout https://halldsvn.jlab.org/trunk/src | + | svn checkout https://halldsvn.jlab.org/repos/trunk/src |
making a directory "src" in the local directory, we would do a | making a directory "src" in the local directory, we would do a | ||
− | svn checkout https://halldsvn.jlab.org/trunk/sim-recon | + | svn checkout https://halldsvn.jlab.org/repos/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?=== |
# everyone would have a directory with a standard name | # everyone would have a directory with a standard name | ||
− | # the tree itself would have a standard name, e. g. " | + | # the tree itself would have a standard name, e. g. "First you check-out sim-recon"<ref>as opposed to "First you check-out src.", "Yes that's what I want to do, but what do I check-out?" ([http://www.youtube.com/watch?v=sShMA85pv8M related video])</ref> |
# related: "src" is non-descriptive | # related: "src" is non-descriptive | ||
#* every package in the known world has a "src" directory | #* every package in the known world has a "src" directory | ||
− | #* there are other packages under trunk | + | #* there are other packages under trunk that do have descriptive names and might contain src directories |
# allows a more descriptive tag, e. g. sim-recon-2010-04-01 | # allows a more descriptive tag, e. g. sim-recon-2010-04-01 | ||
#* like root_5.25.02 | #* like root_5.25.02 | ||
− | # provides a natural home for "helper" directories, e. g., BMS, doc | + | # you can still "checkout trunk/sim-recon/src" if you really want to |
+ | # provides a natural home for "helper" directories, e. g., BMS, doc (this breaks previous item) | ||
===Disadvantages?=== | ===Disadvantages?=== | ||
Line 40: | Line 41: | ||
"sim-recon" is illustrative, could also be | "sim-recon" is illustrative, could also be | ||
+ | * recon-sim | ||
* halld (as in HALLD_HOME) | * halld (as in HALLD_HOME) | ||
* gluex | * gluex | ||
− | * valparaiso | + | * valparaiso (Paradise Valley) |
* lawrenceville | * lawrenceville | ||
* newport-gnus | * newport-gnus | ||
− | * ''etc.'' | + | * ''etc.'' (not literally) |
+ | |||
+ | ---- | ||
+ | |||
+ | <references/> |
Latest revision as of 16:54, 16 March 2010
Contents
What change is being proposed?
Move src to sim-recon/src
Consequences?
Instead of
svn checkout https://halldsvn.jlab.org/repos/trunk/src
making a directory "src" in the local directory, we would do a
svn checkout https://halldsvn.jlab.org/repos/trunk/sim-recon
making a directory "sim-recon" that contains a "src" directory.
Advantages?
- everyone would have a directory with a standard name
- the tree itself would have a standard name, e. g. "First you check-out sim-recon"[1]
- related: "src" is non-descriptive
- every package in the known world has a "src" directory
- there are other packages under trunk that do have descriptive names and might contain src directories
- allows a more descriptive tag, e. g. sim-recon-2010-04-01
- like root_5.25.02
- you can still "checkout trunk/sim-recon/src" if you really want to
- provides a natural home for "helper" directories, e. g., BMS, doc (this breaks previous item)
Disadvantages?
- Not what we are used to; will cause some amount confusion.
- Work will have to be done.
Questions?
- If not now, then when?
- Should HALLD_HOME, HALLD_MY be renamed?
What about the name?
"sim-recon" is illustrative, could also be
- recon-sim
- halld (as in HALLD_HOME)
- gluex
- valparaiso (Paradise Valley)
- lawrenceville
- newport-gnus
- etc. (not literally)
- ↑ as opposed to "First you check-out src.", "Yes that's what I want to do, but what do I check-out?" (related video)