[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sanity.sh patch
From: |
Donald Sharp |
Subject: |
Re: sanity.sh patch |
Date: |
Fri, 3 Nov 2000 16:22:54 -0500 |
User-agent: |
Mutt/1.2.4i |
On Fri, Nov 03, 2000 at 04:13:43PM -0500, Larry Jones wrote:
> Donald Sharp writes:
> >
> > An actual problem with sed( /usr/ucb/sed ) in backuprecover-22.
>
> What version of CVS are you using? As far as I can see,
I'm using 1.11:
donsharp-u5:114> cvs status src/sanity.sh
===================================================================
File: sanity.sh Status: Locally Modified
Working revision: 1.621
Repository revision: 1.621 /home2/cvsroot/ccvs/src/sanity.sh,v
Sticky Tag: cvs1-11 (revision: 1.621)
Sticky Date: (none)
Sticky Options: (none)
Here is the errors spat out:
sed: Unrecognized command: file1
sed: Extra text at end of command: dir/file2
sed: Extra text at end of command: dir/file2
sed: Unrecognized command: file1
FAIL: backuprecover-22
make[1]: *** [check] Error 1
make[1]: Leaving directory `/users/sharpd/distrib/ccvs/src`
make: *** [check] Error 2
This problem goes away when I used the gnu version of sed.
I still have the cvs-sanity test directory around, would you like
to see any particular data in there?
donald
> backuprecover-22 doesn't use sed. And it looks to me like even sed from
> 7th Edition Unix (which is usually held up as the standard for
> portability) could handle everything from sanity.sh.
>
> > I guess my biggest complaint is that sanity.sh is completely dependent
> > on your path, and that I don't see a real good way of getting around
> > this problem....
>
> That's not a problem, it's a feature! (And the way you get around it is
or something ;)
> by changing the path; if not for you, at least for sanity.sh.)
>
> -Larry Jones
>
> I just can't identify with that kind of work ethic. -- Calvin
Re: sanity.sh patch, Derek R. Price, 2000/11/03