Hi All,
I'm trying not to single out any one committer in this admonishment, so it's
just directed in general. If it doesn't apply to you, just ignore it. For
some people it is likely something they may not have thought about, so I'm
bringing it up.
Although Windows is file name case insensitive, both subversion and
unix-like systems are file name case sensitive.
All our source files have to exist on both Windows and Linux, or AIX, or OS
X. So, if you get a little careless with the case when spelling source file
names, things may appear to work fine on Windows, but will fail miserably on
Linux. It can then be a pain to try and straighten things out. Which is
why I'm saying:
* Always cconsider source file names as case sensitive. Always spell the
file name exactly the same regarding the case of the name.
* When adding a new file to the repository from Windows think about how you
want the case of the file name to be, before you commit it.
* Don't mix the case of common extensions. In other words don't suddenly
commit a file like myProgram.Rex. There are dozens of places in the source
code already that have things like: cp *.rex ... Your myProgram.Rex is not
going to work with that copy statement on Linux. It can be hard to track
down why things are failing in these kinds of cases.
* On Windows, if you do want / need to change the case of a committed file
(or directory) it has to be done through svn, not by using the OS to rename
it.
--
Mark Miesfeld
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
