Date: Mon, 15 Sep 2003 08:21:58 +0400 From: Sergey Matveychuk <sem@ciam.ru> To: freebsd-ports@freebsd.org Cc: KATO Tsuguru <tkato@prontomail.com> Subject: Re: PRs ports/56767...56858 Message-ID: <3F653E66.9040601@ciam.ru> In-Reply-To: <3F64D002.5010605@fillmore-labs.com> References: <20030914153245.79ba8838.tkato@prontomail.com> <3F644E7A.1040806@fillmore-labs.com> <20030914230644.447e9891.tkato@prontomail.com> <3F6479F7.6040706@fillmore-labs.com> <20030915023557.5434f58c.tkato@prontomail.com> <3F64D002.5010605@fillmore-labs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Oliver Eikemeier wrote:
> KATO Tsuguru wrote:
>> The function you want is availabe if "ECHO_MSG=${ECHO}" is
>> added to /etc/make.conf. Perhaps this way is appropriate
>> to become default value....
>
>
> Hmmm... I consider it silly if a port tells me
> 'YOU CAN BUILD ME WITH THE FOLLOWING OPTIONS' if I just do
> a makesum or checksum. Most of the ports save me their
> messages, but tell me when something goes wrong. It does not
> work with every port, but I would like it if bento
> builds with -s by default, that will save us the
> repeated option reminders on a lot of ports.
>
> Redefining ECHO_MSG is definetively bad, because it kills
> every error message.
Agree. I think we need to have different ECHO* command: for ports system
messages and errors, and port specific notify messages.
It's not obviously now what I need to use ECHO, ECHO_CMD or ECHO_MSG and
when.
--
Sem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F653E66.9040601>