home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
PROJUP.ZIP
/
PROJUP.DOC
< prev
next >
Wrap
Text File
|
1991-03-24
|
3KB
|
67 lines
ProjectUpdate v1.10 Documentation
ProjectUpdate updates a source and target directories so that all of the
target directory files are synchronized with the source directory. The list
of files on the target directory are found and compared with the
corresponding files on the source directory. If no source file exist the
target file is "fetched" to the source directory. If the target file is
newer the source file is "replaced". If the source file is newer the target
file is "replaced".
- Command Line Options -
If no options are specified the Environment variable PROJUP is used to supply
the options. The default options "/S*.* /Ta:\" are also used.
-s source path (don't include file name) <defaults to "*.*">
-t target path (file name with wild cards only) <defaults to a:\>
-a don't ask before updating source.
-u don't update the source directory
-c don't copy files that are on target but not on source
-r don't update target.
-b beep when done
-v visualize the process only, don't actually copying anything
-d don't show date time of changed file
-e use environment options with these options, environment has precedence
-j journal file, create journal file of copies <defaults to projup.jnl>
-n journal file, append to journal file
-f journal fetches not allowed
-l display License
-h display help
example : projup /j/cb /Ta:\projup
- Target Directory Options -
Because most projects are managed with a version control system,
ProjectUpdate supplies some features that simplify managing files in a
project that are not logged. Normally .obj, .exe, .lib and other files are
not logged in with the version control system since there is no point in
managing changes to these files. However, it is often useful to store these
files on the file server so that each programmer does not need to rebuild
them.
One way to deal with this problem is to have ProjectUpdate manage these
files. The following example shows a batch file that manages updating a
small project.
-----------------------------------------------------
projup /J/EA /S\ver.%ver%\source1 /Td:\ver.%ver%\source1\*.obj,*.res,*.exe
projup /N/EAR /S\ver.%ver%\source1 /Td:\ver.%ver%\source1
projup /N/EA /S\ver.%ver%\source2 /Td:\ver.%ver%\source2\*.obj,*.res,*.exe
projup /N/EAR /S\ver.%ver%\source2 /Td:\ver.%ver%\source2
type ProjUp.jnl | more
-----------------------------------------------------
The preceding example would copy built-up files to the target (probably a
network drive) and bring down any source or built-up files that are newer than
those on the source directory. It would also produce a journal file that is
displayed at the end that lists what happened. An added benefit of this
process is the list of files that can't be copied to the target, but probably
should be "put" with the version control program.