[ On Tuesday, August 8, 2000 at 18:42:49 (-0700), Glew, Andy wrote: ]
> Subject: RE: CVS'ing home directory files; CVS in place
>
> Actually, I will happily use a build procedure,
> if it is reversible.

Hmmm.... reversible...

Do you mean like combining these options to the "install" program with
something in your build system that'll rename the (most recent) backup
copies to their original names and thus effectively undo the most recent
build?

     -b      Backup any existing files before overwriting them by renaming
             them to file.old. See -B for specifying a different backup suf-
             fix.

     -B suffix
             Use suffix as the backup suffix if -b is given. If suffix con-
             tains a '%' sign, a numbered backup will be performed, and the
             %-pattern will be expanded using sprintf(3), given an integer
             counter as the backup number.  The counter used starts from 0,
             and the first available name resulting from the expansion is
             used.

> E.g. once I have checked out the file called
> dir/foo in the repository
> and had it renamed via the build procedure to dir/bar,
> then, if I edit dir/bar,
> I want to have a command that will take the changes
> I make to dir/bar and apply them the file named dir/foo
> in the repository.

I think that's "backwards", if I might say so....

You want to be changing the checked out copy and then installing it into
the "production" location, perhaps after first testing it, and of course
performing any necessary transformations (such as compiling, or
replacing place-holder-tags with site-specific strings, etc.) on the way
through....

> Basically, I am often too lazy,
> and find the process too error-prone
> of editting dir/bar in my workview,
> tracking down that it maps to dir/foo in the repository,
> and then arranging to check it in there.

Ah, but that's where a makefile or some other build and/or install
script makes thing so easy!  It "remembers" everything for you *and* it
takes care of all the messy details and boring redundant steps.  You
just have to invoke it when you're ready and then sit back and relax
while all the magic happens....

> Similarly wrt symlinks, etc. --- any build process
> that is one to one, and even many that just extract info
> from a multiversion form.

?

-- 
                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <[EMAIL PROTECTED]>      <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>

Reply via email to