FW: [Bug 12] gpm-1.19.3 (reply from old maintainer)

Mike B thaz at if.rmci.net
Thu Jul 26 09:26:23 PDT 2001

IMHO, since sed commands are already explained in the lfs book, it would make sense to continue using sed commands.  Perl is a monster all to itself, and may be a potential can of worms....

On the other hand, it offers an opportiunity to introduce basic perl commands, since we are trying to help people learn their linux..

Just my 2-bits...


* Loftus Law: Some people manage by the book, even though they do not know who wrote the book or even which book it is.

-----Original Message-----
FROM: Jesse Tie Ten Quee
TO: blfs-book at linuxfromscratch.org
DATE: Thu 7/26/01 9:36
SUBJECT: Re: FW: [Bug 12] gpm-1.19.3  (reply from old maintainer)


On Thu, Jul 26, 2001 at 11:30:42AM -0400, Jason Gurtz wrote:
> Alessandro suggests a replacment perl command for the sed one also near the
> bottom.  I'll keep you guys posted....

> > It's interesting to hear once again that people is fixing stuff
> > without any coordination with upstream. Actually, that's one of
> > the reasons that made me drop the project.

I find that funny..considering thats what you're trying todo :)

/me doesn't understand some ppl sometimes.

> > >> sed s/OPEN_MAX/FOPEN_MAX/ special.c > special.c~ &&
> > >> mv special.c~ special.c &&

> > 	perl -p -i -e s/OPEN_MAX/FOPEN_MAX/ special.c

> Seems like a good replacment to me.

What about consistency? both ways work, but it would be best to be stay
consistent in this matter, imo.

Jesse Tie Ten Quee - highos at highos dot com

More information about the blfs-book mailing list