Changes between Version 41 and Version 42 of Developers

Timestamp:

2018-06-04T22:10:56+02:00 (6 years ago)

Author:

nicolasmartin

Comment:

--

Developers

@@ -46 +46 @@
 __If your changes are quite modest (one or few routines involved), \\
 you can simply attached in the ticket the output of \\
-any third-party diff tool for easy patching__.
+any third-party diff tool for easy patching with `svn patch`__.
 
 ''Keep in mind that, despite the help we can offer, a certain amount of \\
@@ -55 +55 @@
 === Recommended development installation
 
-After the global reorganisation of the repository, it is now advisable to entirely download the new default development organisation in your 
+After the global reorganisation of the repository, it is now advisable to entirely download the new default development organisation in your local computing architecture:
 * [browser:/NEMO/trunk]: ''the main development branch''
 * [browser:/NEMO/branches]
@@ -62 +62 @@
 * [browser:/NEMO/releases]: ''all official NEMO releases'', '''only the last one is maintained'''
 
+The first checkout will be a bit longer than usual but the SVN commands will be much simpler: the modifications will be done locally and not directly to the repository by committing with former complex `svn+ssh` syntax. See [wiki:/Developers/SVNHowTo#Basics SVN basics] for more.
+
 {{{#!sh
-# One step  method: download directly a copy with write access) or
+# One step  method: download directly a copy with write access or
 svn co svn+ssh://"ID"@forge.ipsl.jussieu.fr/ipsl/forge/projets/nemo/svn/NEMO [...]
 # Two steps method: download a read-only copy and switch to developer when 
 # * you have your developer access or
-# * a backup of the work by committing to the repository is required
+# * a backup of the work is required by committing to the repository
 svn co http://forge.ipsl.jussieu.fr/nemo/svn/NEMO  [...]
-...
+......
 svn sw --relocate http://forge.ipsl.jussieu.fr svn+ssh://"ID"@forge.ipsl.jussieu.fr/ipsl/forge/projets
 }}}
 
-=== 
+=== New build of the working copy
 
-If needed, you can learn the new [wiki:Developers/SVN_HowTo SVN basics] to work with the repository. 
+To facilitate the development work by simplifying the management and the sharing of the code in the repository, while ensuring the consistency of the working copies, we have introduced the [http://svnbook.red-bean.com/en/1.7/svn.advanced.externals.html SVN externals definitions] in the building of the working copies. \\
+We have identified the core code and the complementary codes of NEMO, the latter which is developing less rapidly than the NEMO core has been extracted from the development organisation of the repository (`branches` / `releases` / `trunk`) to different locations of the repository.
+
+From now on, a working copy of the NEMO reference is the summation of few checkouts from different sources defined by the `svn:externals` properties of the working copy. \\
+Here is 
+
+{{{#!sh
+# Relative URL                 
+# '^' for repository root
+^/utils/build/arch"[@REV]"     arch       # FCM configuration file for generic computing architectures
+^/utils/build/makenemo"[@REV]" makenemo   # Bash main script for building a NEMO configuration
+^/utils/build/mk"[@REV]"       mk         # Bash sub-scripts and FCM input files for compiling
+^/utils/tools"[@REV]"          tools      # User tools
+^/vendors/AGRIF/dev"[@REV]"    ext/AGRIF  # NEMO dependency for nesting
+^/vendors/FCM"[@REV]"          ext/FCM    #  ""      ""     for source code compilation
+^/vendors/IOIPSL"[@REV]"       ext/IOIPSL #  ""      ""     for IO management
+}}}
+
+If you have to modify these properties in your working copy, you can learn the new [wiki:Developers/SVNHowTo SVN basics] to work with the repository. 
 
 == Development activities