Date: Tue, 22 Feb 2000 01:35:37 +0900 From: "Akinori -Aki- MUSHA" <knu@idaemons.org> To: tkato@prontomail.ne.jp Cc: honda@kashio.info.mie-u.ac.jp, freebsd-ports@FreeBSD.ORG Subject: Re: ports/16863: new port japanese/esecanna-wnn6 Message-ID: <86k8jy344m.wl@archon.local.idaemons.org> In-Reply-To: In your message of "Tue, 22 Feb 2000 01:08:32 %2B0900" <1DCA79B8E48E3D1178030005B8672B34@tkato.prontomail.ne.jp> References: <1DCA79B8E48E3D1178030005B8672B34@tkato.prontomail.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi.
At Tue, 22 Feb 2000 01:08:32 +0900,
KATO Tsuguru <tkato@prontomail.ne.jp> wrote:
> > +do-configure:
> > + @cd ${WRKSRC} && perl -i -pe "s,!!PREFIX!!,${PREFIX},g" constdef.h
>
> do-configure:
> @${PERL} -i -pe "s,!!PREFIX!!,${PREFIX},g" ${WRKSRC}/constdef.h
>
> would be better.
But this was intensional. I suggested him to process more files
here to avoid having a lot of patches which stands only for _regular_
substitutions. My esecanna-vje30 port is the very example.
> At least, if you want to run perl within port's Makefile,
> you have to use it as "${PERL}".
Is that so? I've seen so many hardcoded perl's in other ports
Makefiles and portlint does not complain about it at all.
But from now I'll conform myself that rule, the right thing.
--
/
/__ __
/ ) ) ) ) /
Akinori -Aki- MUSHA aka / (_ / ( (__( <knu@idaemons.org>
"If you choose not to decide you still have made a choice."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86k8jy344m.wl>