[Svnmerge] svnmerge and different flavors of sh

[Castellow, Robert]

Thanks guys!  That fixed the "for" loop but there appears to be other
issues.  

There also appear to be differences in the SunOS grep.  I tried using
the /usr/bin/grep and also the /usr/xpg4/bin/grep by specifically
calling these versions, but each attempt had options were still
incorrect.

Output:
soegadm @ sogbst4--> ../svnmerge avail
grep: illegal option -- E
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- E
Usage: grep -hblcnsviw pattern file . . .
Usage: grep -hblcnsviw pattern file . . .
../svnmerge: URL:: not found
svn: Write error: Broken pipe

I will keep plugging away at this.  

Thanks,
Rob Castellow



-----Original Message-----
From: Blair Zajac [mailto:blair at orcaware.com] 
Sent: Friday, September 02, 2005 12:59 PM
To: Archie Cobbs
Cc: svnmerge at orcaware.com; Castellow, Robert
Subject: Re: [Svnmerge] svnmerge and different flavors of sh

Archie Cobbs wrote:
> Blair Zajac wrote:
> 
>>> Castellow, Robert wrote:
>>>
>>>> soegadm @ sogbst4--> ../svnmerge init -s -v -r 0-1503
>>>> svn://90.34.7.118/soeg/branches/R18.0/trunk
>>>>
>>>> ../svnmerge: syntax error at line 561: `;' unexpected
>>>
>>>
>>> Looks like there is some incompatibility on Solaris. These things
>>> are fixed as they come up. If you can figure out a patch that makes
>>> it work for you, I'll test it out for bash compatibility.
>>
>>
>> Maybe try something like this:
>> Index: svnmerge
>> ===================================================================
>> --- svnmerge    (revision 16027)
>> +++ svnmerge    (working copy)
>> @@ -558,7 +558,7 @@
>>  [ $? = 0 ] || usage
>>  set -- ${ARGS}
>>
>> -for i; do
>> +for i in $@; do
>>      case "$i" in
> 
> 
> Thanks.. I just committed a slightly modified version of this fix
> (using "$@" instead of plain $@).
> 
> -Archie

Great.  You may want to add an entry in

http://svn.collab.net/repos/svn/branches/1.2.x/STATUS

to get this fix into the next Subversion 1.2.4 release.

Regards,
Blair

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. 163