Changes between Version 16 and Version 17 of AlsprocDevelopment


Ignore:
Timestamp:
Mar 25, 2015 8:22:54 AM (4 years ago)
Author:
dac
Comment:

Changed SVN section to Git

Legend:

Unmodified
Added
Removed
Modified
  • AlsprocDevelopment

    v16 v17  
    4242Ideally in future this would be implemented entirely in the C program. The reason this isn't the case now is because of the effort involved in passing meta data into and around the program. This kind of problem weighs in favour of implementing a reader for .cfg files in alsproc and allowing components in the program to query the reader as they require. Otherwise, the maintainer will face the problem of keeping within the character limit for each line of Bash in passing arguments into alsproc directly via command line. This kind of solution is part of a bigger discussion which has not yet been resolved, justifying the semi-temporary solution currently in-place.
    4343
    44 == Subversion ==
     44== Git ==
    4545
    46 Alsproc can be found in subversion under tools/alsproc. Obtain a copy with svn checkout.
     46Alsproc is in a separate git repository, you can clone using:
    4747{{{
    48 svn checkout https://rsg.pml.ac.uk/intranet/svnroots/arsf-internal/trunk/tools/alsproc
     48git clone -v https://$USER@rsg.pml.ac.uk/intranet/gitrepos/arsf/internal_only/alsproc.git
    4949}}}
    50 
    51 You can make and manage your changes in this checkout. When you've tested it and you're happy, you may need to advance the version number. Edit the Makefile in src/, and find the line which says vers=x.x.x and advance it as you need.
    52 {{{
    53 # VERSION NUMBER
    54 vers=0.0.9
    55 }}}
    56 
    57 When you're satisfied, commit the changes.
    58 {{{
    59 svn commit
    60 }}}
    61 
    62 And finally, tag the branch version if you advanced the version number.
    63 {{{
    64 svn cp https://rsg.pml.ac.uk/intranet/svnroots/arsf-internal/trunk/tools/alsproc https://rsg.pml.ac.uk/intranet/svnroots/arsf-internal/tags/alsproc-0.0.9 -m "tagging new version of alsproc"
    65 }}}
     50Make changes in a separate branch (forked from 'development-branch') and go through code review to get these merged into the development branch. For releases, merge changes into the master branch and tag.
    6651
    6752== Testing ==
     
    8570}}}
    8671
    87 Current policy is to install in the home directory of the arsf user, as this asserts that all users across the department are using the same and current version of alsproc. Enter usr/opt/alsproc and check out the version you wish to build, check out the repository, compile it, and install it locally using the purpose-built Makefile rule: arsf_install.
    88 
    89 {{{
    90 cd ~arsf/usr/opt/alsproc
    91 svn checkout https://rsg.pml.ac.uk/intranet/svnroots/arsf-internal/tags/alsproc-0.0.9
    92 cd alsproc-0.0.9/src
    93 make
    94 make arsf_install
    95 }}}
     72Current policy is to install in the home directory of the arsf user, as this asserts that all users across the department are using the same and current version of alsproc.
    9673
    9774== To Do ==