From: Bob G. <bo...@rc...> - 2007-07-29 04:12:05
|
This is more on the subject of Subversion and sql-ledger Attached is a script for doing sql-ledger version upgrades and keeping all the files (with your own tweeks too) under version control. The script follows the block diagram below: # /usr/local/sql-ledger svnrepos (directories below within repos) # --------------------- --------------------------------- # (STEP1) import # vendor v 2.8.5 ->->->->-> /vendor/sql-ledger/current # # <-<-< /vendor/sql-ledger/current # v # (STEP2) copy | tag # v # >->-> /vendor/sql-ledger/sql-ledger-2.8.5 # # <-<-< /vendor/sql-ledger/sql-ledger-2.8.5 # v # (STEP3) copy | to main # v # >->-> /sql-ledger/ # (STEP4) # rm -rf # <-<-< /sql-ledger/ # checkout # /usr/local/sql-ledger <-<-| # | # V # ------------------- # | external update | (STEP5) # | to v 2.8.6 | # ------------------- # | # V (STEP6) Backup and inspect the new 2.8.6 update # | # /usr/local/sql-ledger ->->-> # v # (STEP7) svn_load_dirs # v # >->-> /vendor/sql-ledger/current # # <-<-< /vendor/sql-ledger/current # v # copy | tag (done as part of above command # v # >->-> /vendor/sql-ledger/sql-ledger-2.8.6 # # <-<-< /vendor/sql-ledger/sql-ledger-2.8.5 # v # <-<-< /vendor/sql-ledger/current # v # (STEP8) merge # v # >->-> /sql-ledger/ # # (STEP9) commit On Thu, 2007-07-12 at 12:45 -0500, Bob Gustafson wrote: > If you have been tempted to make changes to the sql-ledger code to > respond to local requirements, using svn as your source code control > system offers an 'easy' way to handle your changes and the upgrade to > new versions when they come out. > > This piece of the svn handbook outlines the approach: > > http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html > > ------------------------------------------------------------------------- |