Changeset 418
- Timestamp:
- 09/18/2009 13:09:36 (3 years ago)
- Location:
- branches/confman-1.9
- Files:
-
- 7 edited
-
. (modified) (1 prop)
-
Makefile.am (modified) (1 diff)
-
configure.ac (modified) (1 diff)
-
confman.8.in (modified) (1 diff)
-
confman.in (modified) (1 diff)
-
confmandoc.sh (modified) (2 diffs)
-
confmanlib.sh.in (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
branches/confman-1.9
-
branches/confman-1.9/Makefile.am
r397 r418 1 1 BASH = @BASH_SHELL@ 2 3 VERSION += (397)4 2 5 3 bashcompdir = $(sysconfdir)/bash_completion.d -
branches/confman-1.9/configure.ac
r390 r418 1 1 AC_PREREQ(2.62) 2 AC_INIT([confman], [1.9. a], [confman-users@timesinks.net])2 AC_INIT([confman], [1.9.2b], [confman-users@timesinks.net]) 3 3 AM_INIT_AUTOMAKE([foreign]) 4 4 -
branches/confman-1.9/confman.8.in
r388 r418 110 110 .Nm . 111 111 It will check out your working copy. setup takes no additional arguments. 112 .It Cm update 112 .It Cm update [ Ar options ] 113 113 The update command will update all the modules in your working copy. This 114 command does not alter the repository or the system. 114 Any options specified will be passed directly to 115 .Xr svn 1 . This can be used 116 for updating your working copy to an older revision. 117 118 For example, you could use `confman update -r '{20090801}' www` to look at the 119 state of the module named `www' as of 1 August 2009. This will re-add any 120 deleted files and delete any added files from your working copy (This is 121 simplest if you have commited any outstanding changes, but subversion is good 122 about not deleting work-in-progress -- the errors can just be confusing). 123 124 Note that before any install or commit operation, there is an implicit update 125 that will cause the latest repository revision to be reflected in your working 126 copy. command does not alter the repository or the system. 115 127 .It Cm commit 116 128 The commit command causes your changes to take effect. -
branches/confman-1.9/confman.in
r388 r418 98 98 99 99 function update { 100 if [ -z "$*" ] ; then 101 conf_lock_wcopy 102 conf_update_tree || exit 1 103 conf_unlock_wcopy 104 else 105 print_usage 1 106 fi 100 conf_lock_wcopy 101 conf_update_tree "$@" || exit 1 102 conf_unlock_wcopy 107 103 } 108 104 -
branches/confman-1.9/confmandoc.sh
r355 r418 36 36 $MYNAME [ help | -h ] [ command ] 37 37 $MYNAME setup 38 $MYNAME update 38 $MYNAME update [ options ] 39 39 $MYNAME commit 40 40 $MYNAME diff [ working_copy ] … … 135 135 136 136 Usage: 137 $MYNAME update 138 139 The update command will update your working copy of all the modules 140 appearing in the current host's recipe file. This command does not alter 141 the repository. 137 $MYNAME update [ options ] 138 139 With no arguments, the update command will update your working copy of all 140 the modules appearing in the current host's recipe file. This command does 141 not alter the repository. 142 143 Any options specified will be passed directly to svn(1). This can be used 144 for updating your working copy to an older revision. Note that before any 145 install or commit operation, there is an implicit update that will cause 146 the latest repository revision to be reflected in your working copy. 142 147 143 148 EOF -
branches/confman-1.9/confmanlib.sh.in
r415 r418 117 117 # Updates the whole source tree 118 118 function conf_update_tree { 119 @SVN@ update ${WORK_PATH} 119 if [ -z "$*" ] ; then 120 @SVN@ update ${WORK_PATH} 121 else 122 @SVN@ update "$@" 123 fi 120 124 } 121 125
Note: See TracChangeset
for help on using the changeset viewer.
