Date: Fri, 14 Jun 2002 15:01:21 +0300 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Trevor Johnson <trevor@jpj.net> Cc: Juli Mallett <jmallett@FreeBSD.ORG>, Pete Fritchman <petef@absolutbsd.org>, portmgr@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: ports/Mk bsd.port.mk Message-ID: <3D09DB11.8362727A@FreeBSD.org> References: <20020614033017.I8221-100000@blues.jpj.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Trevor Johnson wrote: > > Juli Mallett wrote: > > > Anyway, it's on my list of things to MFC, but it was controversial when it was > > on the tip of my mind, and I had trivial stuff I was having trouble getting to > > the RELENG_4 branch during the freeze, so I decided I'd wait for the free for > > all. I'd like to see ports move over to using it once it's been MFC'd for a > > while... > > Suppose there were a port, call it ports/misc/46upgrade, which installed > jmallett's sed, either as "jsed" or as just plain "sed" (in the latter > case, it would /usr/bin/sed aside on installation, and back in place on > deinstallation). Suppose the jsed port bumped /var/db/port.mkversion and > bsd.port.mk checked for this ("your system is too old to use this > bsd.port.mk") Then the macro for patching in situ could always use > jmallett's sed, never perl. It would behave consistently across different > versions of FreeBSD, so it would be easier to test and debug. I should admit that it looks like the most realistic plan out there. The main problems are with $ and @ characters, which have a special meaning for perl but no such meaning for sed(1), so that any, even simple, regexp that uses those chars *could not* be modified to work uniformly with both perl and sed. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D09DB11.8362727A>