Matt Swift <[EMAIL PROTECTED]> writes:
> The idea of a predefined method for every conceivable configuration
> will have to be abandoned sooner or later. Even with 1.149, all the
> logical permutations are not there, and I had to add my own to get an
> extra argument to rsync when the remote binary is in ~/bin not a std
> system path.
Okay, okay. I already did some work to find the right shell and
stuff. It seems logical to extend this to find the right uuencode
syntax. Hm.
Can you all do "uudecode --version 2>/dev/null ; echo $?" and tell me
what you see?
On Solaris 2.6, I get exit status 2, and I have to use the "-p" thing.
On Linux, I get a line saying GNU sharutils and exit status 0, and I
have to use the "-o -" thing. Don't have access to FreeBSD at the
moment. Don't have access to HP-UX, AIX, A/UX, Irix at all. So if
this is sufficient, then I can add stuff to the connection setup which
determines the uudecode version and then selects the right syntax to
use. Good.
kai
--
Life is hard and then you die.
