Date: Sat, 24 Apr 2004 23:41:26 +0700 (NOVST)
From: Alexey Dokuchaev <danfe@regency.nsu.ru>
To: FreeBSD-gnats-submit@FreeBSD.org
Subject: ports/65931: Typo in message ("port is depricated" warning) in bsd.port.mk
Message-ID: <200404241641.i3OGfQ9W079957@regency.nsu.ru>
Resent-Message-ID: <200404241650.i3OGoEM9067039@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 65931
>Category: ports
>Synopsis: Typo in message ("port is depricated" warning) in bsd.port.mk
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Apr 24 09:50:14 PDT 2004
>Closed-Date:
>Last-Modified:
>Originator: Alexey Dokuchaev
>Release: FreeBSD 4.9-STABLE i386
>Organization:
CNIT NSU
>Environment:
System: FreeBSD regency.nsu.ru 4.9-STABLE FreeBSD 4.9-STABLE #1: Wed Mar 3 13:17:54 NOVT 2004 root@regency.nsu.ru:/usr/src/sys/compile/REGENCY i386
>Description:
When bpm emits message like "this port is scheduled to be removed
bla-bla-bla" it's not really linguistically correct. IMHO, this phrase
should be changed to "this port is scheduled to be removed *on*
bla-bla-bla" to make it sound better and more ear/eye-appealing. This
is purely cosmetic though.
>How-To-Repeat:
Try building any port with EXPIRATION_DATE defined and read the
message.
>Fix:
%%%
--- bsd.port.mk.orig Sat Apr 24 17:13:54 2004
+++ bsd.port.mk Sun Apr 25 00:55:48 2004
@@ -2760,7 +2760,7 @@
@${ECHO_MSG} "${DEPRECATED}."
@${ECHO_MSG}
.if defined(EXPIRATION_DATE)
- @${ECHO_MSG} "It is scheduled to be removed ${EXPIRATION_DATE}."
+ @${ECHO_MSG} "It is scheduled to be removed on ${EXPIRATION_DATE}."
@${ECHO_MSG}
.endif
.endif
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404241641.i3OGfQ9W079957>