we could create a tar exploder as shell script for the change that
would just unpack the tar to $LPS_HOME<where the tar was created>,
and I bet tar even has a feature to make a backup when it replaces a
file...
On 2006-11-30, at 12:44 EST, Benjamin Shine wrote:
There are two ways to apply a changeset.
Mechanism #1 is reliable but may destroy local changes, if there
are changes to the same file. Explode the tar, uncompress
files.tar, figure out where in the source tree files.tar is rooted,
then copy the files in files.tar into your lps tree. HOWEVER this
will overwrite locally-modified files; do NOT do it if you have
local changes in the files this changeset changes. This mechanism
will not delete files that the changeset schedules for deletion;
this is a bug.
Mechanism #2 is a little bit more fiddly but won't destroy local
changes. It won't properly add, delete, or move files added,
deleted or moved by the changeset; only patch them. Explode the
tar, then figure out where the changeset is rooted from. In your
lps tree, cd to the corresponding source directory. Then call /path/
to/changeset/apply.sh. It will attempt to modify the local files
with the patches. It will complain noisily if it has trouble
applying the patches.
I recommend #1, but only ever do it to a working copy which does
not have any local changes that you care about, so you do not risk
overwriting your own changes.
-ben
Benjamin Shine
Software Engineer, Open Laszlo / Laszlo Systems
[EMAIL PROTECTED]
