Advice on handing common code

2013-01-08 Thread C M 
All,


I am setting up a new repository and have a question on how to handle
“common” code. Common refers to code which is shared across the multiple
systems that we deploy.



In addition to the common code, we also have system-specfic software
(custom code).



Given the typical SVN layout, what’s a recommended way to manage this,
especially when creating release tags?



In this model, we include the



/trunk/common_version1/application_1

../../application_2

./../application_3



/trunk/system1/application_1

../../application_2

../../application_3



/tags/system1/Rel_1 [where this may include the system1 apps plus
common_version1/application_1 and application 3]



../system2/application_1

../system2/application_2

../system2/application_3



/tags/system2/Rel_1 [where this may include system2 apps plus
common_version1/application_1, application_2 and application3]

RE: Advice on handing common code

2013-01-08 Thread John Maher 
I use the externals property for my common code.

http://www.visualsvn.com/support/svnbook/advanced/externals/

 

 



From: C M [mailto:cmanalys...@gmail.com] 
Sent: Tuesday, January 08, 2013 11:43 AM
To: users@subversion.apache.org
Subject: Advice on handing common code

 

All,

 

I am setting up a new repository and have a question on how to handle
"common" code. Common refers to code which is shared across the multiple
systems that we deploy. 

 

In addition to the common code, we also have system-specfic software
(custom code). 

 

Given the typical SVN layout, what's a recommended way to manage this,
especially when creating release tags? 

 

In this model, we include the 

 

/trunk/common_version1/application_1

../../application_2

./../application_3

 

/trunk/system1/application_1

../../application_2

../../application_3

 

/tags/system1/Rel_1 [where this may include the system1 apps plus
common_version1/application_1 and application 3]

 

../system2/application_1

../system2/application_2 

../system2/application_3  

 

/tags/system2/Rel_1 [where this may include system2 apps plus
common_version1/application_1, application_2 and application3]

RE: Advice on handing common code

2013-01-08 Thread Brenden Walker 
If you have multiple projects that may edit the shared code I would recommend 
treating it as vendor code: 
http://www.visualsvn.com/support/svnbook/advanced/vendorbr/

We do that with multiple in-house projects run by multiple departments and it 
allows us to share changes via merging.

From: John Maher [mailto:jo...@rotair.com]
Sent: Tuesday, January 08, 2013 12:37 PM
To: C M; users@subversion.apache.org
Subject: RE: Advice on handing common code

I use the externals property for my common code.
http://www.visualsvn.com/support/svnbook/advanced/externals/



From: C M [mailto:cmanalys...@gmail.com]
Sent: Tuesday, January 08, 2013 11:43 AM
To: users@subversion.apache.org
Subject: Advice on handing common code

All,

I am setting up a new repository and have a question on how to handle "common" 
code. Common refers to code which is shared across the multiple systems that we 
deploy.

In addition to the common code, we also have system-specfic software (custom 
code).

Given the typical SVN layout, what's a recommended way to manage this, 
especially when creating release tags?

In this model, we include the

/trunk/common_version1/application_1
../../application_2
./../application_3

/trunk/system1/application_1
../../application_2
../../application_3

/tags/system1/Rel_1 [where this may include the system1 apps plus 
common_version1/application_1 and application 3]

../system2/application_1
../system2/application_2
../system2/application_3

/tags/system2/Rel_1 [where this may include system2 apps plus 
common_version1/application_1, application_2 and application3]

Question regarding "@" symbol

2013-01-08 Thread Leonard Wayne 
Hello.

I read the Subversion documentation (in 
particular the "Peg and Operative Revisions"
section) for how to handle versioning of
directories with names that contain the "@"
symbol.  But I am still confused by something.

I want to use the "import" command to import a 
tree that includes subdirectories with names
that contain the "@" symbol.  For example I
would like to do the following (using the
Windows syntax):

svn import c:\myPath\myDirTree file:///c:/svn/repo/myProject -m "Initial 
import."

The directory tree "myDirTree" contains 
subdirectories with names that contain the "@"
symbol.

The command executes without reporting any
problems.

But is it OK to use this command?  Or instead
of using the "import" command should I instead
do a bunch of "add" commands and use the 
workaround discussed in the "Peg and Operative
Revisions" section of the manual (append "@"
at the end of the path)?

The reason I cannot avoid using directories
whose names contain "@" is that Matlab has
users place class-based code in directories
whose name begins with "@".

Thank you in advance.

- Len

Subversion 1.6.20 released

2013-01-08 Thread Ben Reser 
I'm happy to announce the release of Apache Subversion 1.6.20.
Please choose the mirror closest to you by visiting:

http://subversion.apache.org/download/#supported-releases

The SHA1 checksums are:

215083e6fc367b46fa76be82841115a32f0a5766 subversion-1.6.20.tar.gz
6b2af448dbc20b36099d1309f1715421192d327f subversion-1.6.20.tar.bz2
8b5fd5d187a89cc8009e8219b955c25dff3f871b subversion-1.6.20.zip

PGP Signatures are available at:

http://subversion.tigris.org/downloads/subversion-1.6.20.tar.gz.asc
http://subversion.tigris.org/downloads/subversion-1.6.20.tar.bz2.asc
http://subversion.tigris.org/downloads/subversion-1.6.20.zip.asc

For this release, the following people have provided PGP signatures:

   Ben Reser [4096R/16A0DE01] with fingerprint:
19BB CAEF 7B19 B280 A0E2  175E 62D4 8FAD 16A0 DE01
   Branko Čibej [2048R/C8628501] with fingerprint:
8769 28CD 4954 EA74 87B6  B96C 29B8 92D0 C862 8501
   Johan Corveleyn [4096R/010C8AAD] with fingerprint:
8AA2 C10E EAAD 44F9 6972  7AEA B59C E6D6 010C 8AAD
   Mark Phippard [1024D/035A96A9] with fingerprint:
D315 89DB E1C1 E9BA D218  39FD 265D F8A0 035A 96A9
   Paul T. Burba [4096R/56F3D7BC] with fingerprint:
1A0F E7C6 B3C5 F8D4 D0C4  A20B 64DD C071 56F3 D7BC
   Philip Martin [2048R/ED1A599C] with fingerprint:
A844 790F B574 3606 EE95  9207 76D7 88E1 ED1A 599C
   Stefan Sperling [2048R/9A59B973] with fingerprint:
8BC4 DAE0 C5A4 D65F 4044  0107 4F7D BAA9 9A59 B973

Release notes for the 1.6.x release series may be found at:

http://subversion.apache.org/docs/release-notes/1.6.html

You can find the list of changes between 1.6.20 and earlier versions at:

http://svn.apache.org/repos/asf/subversion/tags/1.6.20/CHANGES

Questions, comments, and bug reports to users@subversion.apache.org.

Thanks,
- The Subversion Team

Re: Question regarding "@" symbol

2013-01-08 Thread Blair Zajac 

On 01/08/2013 12:11 PM, Leonard Wayne wrote:

Hello.

I read the Subversion documentation (in
particular the "Peg and Operative Revisions"
section) for how to handle versioning of
directories with names that contain the "@"
symbol.  But I am still confused by something.

I want to use the "import" command to import a
tree that includes subdirectories with names
that contain the "@" symbol.  For example I
would like to do the following (using the
Windows syntax):

svn import c:\myPath\myDirTree file:///c:/svn/repo/myProject -m "Initial 
import."


This will work.  The only issue with @ is when it appears in a command 
line.  Anytime you reference one of the directories with a @ in its 
name, then you'll need to append a @ at the end.



The directory tree "myDirTree" contains
subdirectories with names that contain the "@"
symbol.

The command executes without reporting any
problems.

But is it OK to use this command?  Or instead
of using the "import" command should I instead
do a bunch of "add" commands and use the
workaround discussed in the "Peg and Operative
Revisions" section of the manual (append "@"
at the end of the path)?


No, just use import.

BTW, I don't like import for a different reason is that there's no 
forgiveness for errors, say if you've left a file in the directory you 
don't want to import.  I like to do a recursive add instead for that reason.


Regards,
Blair