Changes between Version 1 and Version 2 of IndependentLibraryVersioning


Ignore:
Timestamp:
Jun 7, 2007, 6:19:49 AM (15 years ago)
Author:
Gennadiy Rozental
Comment:

snv->svn

Legend:

Unmodified
Added
Removed
Modified

  • IndependentLibraryVersioning

    v1 v2  
    1     {{{
     1{{{
    22#!html
    33<h1 style="font-size: 180%; text-align: center;">Independent libraries versioning proposal for boost development environment, testing and release procedures</h1>
    … …  
    66== Introduction ==
    77
    8 This document presents the proposal for [#snv_structure restructuring] boost development environment along with new [#test_procedures testing] and [#release_procedures release] procedures. The primary idea of this proposal is to "bite the bullet" and completely separate boost into multiple independent components and use [#independent_versioning independent versioning] for each one.
     8This document presents the proposal for [#svn_structure restructuring] boost development environment along with new [#test_procedures testing] and [#release_procedures release] procedures. The primary idea of this proposal is to "bite the bullet" and completely separate boost into multiple independent components and use [#independent_versioning independent versioning] for each one.
    99
    1010== Objectives ==
    … …  
    2828* It is easy to release of subsets of Boost
    2929
    30 == SNV repository structure == #snv_structure
     30== SVN repository structure == #svn_structure
    3131
    3232The repository structure have to be changed to reflect an "independent nature" of this proposal. Essentially the change convert existing boost tree that look like this:
    … …  
    6363}}}
    6464
    65 The SNV repository directory structure for every library should look like this:
     65The SVN repository directory structure for every library should look like this:
    6666
    6767{{{
    … …  
    115115}}}
    116116
    117 To support the need for a single command update of several (all) boost libraries it might be convenient to create combined boost tree (similar to our current tree) using snv externals based reflections.
     117To support the need for a single command update of several (all) boost libraries it might be convenient to create combined boost tree (similar to our current tree) using svn externals based reflections.
    118118
    119119{{{
    … …  
    234234== Development/testing environment == #dev_tree
    235235
    236 The environment used by developers and testers can represent a subset of SNV repository and only refer to the libraries/versions actually used:
     236The environment used by developers and testers can represent a subset of SVN repository and only refer to the libraries/versions actually used:
    237237
    238238{{{
    … …  
    259259
    260260If build target depends on the libX:Nx and the version Nx of the library libX is not present in development environment
    261 boost make system pulls it automatically from the snv and place in an appropriate location.
     261boost make system pulls it automatically from the svn and place in an appropriate location.
    262262
    263263For the header only library there should be a way to define the target in build/Jamfile that does only that dependencies fetching.