Re: [Oorexx-devel] Important Note about svn update for 4.0 commits revison 92 - 95

[Mark M. <mie...@ac...>]

Rony G. Flatscher wrote:

: Also, you can create/write ooRexx scripts to do that (and much more),
: the aforeposted Bachelor work has the details (and a few quite nice
: ideas), the PDF is easily downloaded and skimmed through.
: 
: Personally, I do a two step move: rename the file to file0 
: and then from
: file0 to File. Maybe an ooRexx script could be created to do that...
: ;)

Rony,

I'll take a look at your students work, when I get some time.  <grin> I
still have you latest BS4Rexx sitting, unzipped, in my queue.

The problem of changing the case, is not a problem for the person doing the
changing.  As I understand it, the problem would be for someone else trying
to update their working copy on a Windows box.

For example:

svn move classfactory.cpp _classfactory.cpp
svn move _classfactory.cpp ClassFactory.cpp

Would leave my working copy in fine shape.  But, for someone else trying to
do an update, they would have a problem.  If they tried:

E:\work.ooRexx\4.0\interpreter> svn update
extensions\platform\windows\orxscrpt

They would get this message:

svn: Failed to add file
'extensions\platform\windows\orxscrpt\ClassFactory.cpp': object of the same
name already exists

I was afraid I would do the change, and then others would have a hard time
doing an update.  I had searched through the subversion mailing lists and
there are several horror stories about people getting their working copies
in states they couldn't recover from in this situation.

But, it was an unfounded fear.  <grin>

--
Mark Miesfeld
mie...@ac...