New URL for NEMO forge!

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
Changeset 11709 – NEMO

Changeset 11709

2019-10-16T20:57:29+02:00 (5 years ago)

Choose a more appropriate name to identify the starting space to take the first steps as developer

Instead of collecting one by one your branches with several checkouts,
I suggest to download this developer directory to install a lightweight but working development environment in order to handle all your developments in one local working copy.

$ svn co

Then run the shell script to do once for all a single checkout from
the SVN repository

$ ./ [ID]        # Create './NEMO_dev'  folder mimicking '/NEMO' on the repo
$                                  # (development of the NEMO core with 'trunk', 'branches' & 'releases'
$ ./ repo [ID]   # Create './NEMO_repo' folder mimicking the entire repo (/)
$                                  # (including source code defined as externals: AGRIF, tools, etc...)

In any case, the trunk and the latest release will be downloaded entirely.
Add your developer username (ID) to already have the right URL scheme for committing:
svn+ssh://... instead of default http://... (no need to launch svn sw --relocate ... later).

From that, the SVN operations will be much simpler with UNIX-like SVN cmds (svn {cp,ls,mv,rm} ...) before pushing the changes to the repository with the usual svn ci ....
To know how to manage your working copy (create, download and delete a branch), see README at the root.

1 moved

Note: See TracChangeset for help on using the changeset viewer.