aboutsummaryrefslogtreecommitdiffstats
path: root/Mk
diff options
context:
space:
mode:
authoradamw <adamw@FreeBSD.org>2006-01-17 02:28:35 +0800
committeradamw <adamw@FreeBSD.org>2006-01-17 02:28:35 +0800
commitfdb54c961202eda86294a31657083b87e9c50d27 (patch)
tree83d6c5494c593dea1e2d7701d09077b3f2bc73ee /Mk
parenta07e5af767746f311c432d731881beab6a37d40e (diff)
downloadfreebsd-ports-gnome-fdb54c961202eda86294a31657083b87e9c50d27.tar.gz
freebsd-ports-gnome-fdb54c961202eda86294a31657083b87e9c50d27.tar.zst
freebsd-ports-gnome-fdb54c961202eda86294a31657083b87e9c50d27.zip
Grammar fixes.
Don't worry, mezz, you have other good qualities ;;-)
Diffstat (limited to 'Mk')
-rw-r--r--Mk/bsd.gnome.mk2
1 files changed, 1 insertions, 1 deletions
diff --git a/Mk/bsd.gnome.mk b/Mk/bsd.gnome.mk
index 7334f77e01c2..7ebdb35904d3 100644
--- a/Mk/bsd.gnome.mk
+++ b/Mk/bsd.gnome.mk
@@ -702,7 +702,7 @@ PLIST_SUB+= GNOMEDESKTOP:="@comment " NOGNOMEDESKTOP:=""
.endif
.if ${MAINTAINER}=="gnome@FreeBSD.org"
-CONFIGURE_FAIL_MESSAGE= "Please run the gnomelogalyzer, available from \"http://www.freebsd.org/gnome/gnomelogalyzer.sh\", which will diagnose the problem and suggest a solution. If - and only if - the gnomelogalyzer cannot solve the problem, report the build failure to the FreeBSD GNOME team at ${MAINTAINER}, and attach (a) \"${CONFIGURE_WRKSRC}/${CONFIGURE_LOG}\", (b) the output of the failed make command, and (c) the gnomelogalyzer output. Also, it might be a good idea to provide an overview of all packages installed on your system (i.e. an \`ls ${PKG_DBDIR}\`). Make sure to put your attachment in either website, copy-n-paste in http://freebsd-gnome.pastebin.com, or send-pr with attachment. Try to avoid sending any attachments to the mailing list (${MAINTAINER}), because attachments sent to FreeBSD mailing lists are usually discarded by the mailing list software."
+CONFIGURE_FAIL_MESSAGE= "Please run the gnomelogalyzer, available from \"http://www.freebsd.org/gnome/gnomelogalyzer.sh\", which will diagnose the problem and suggest a solution. If - and only if - the gnomelogalyzer cannot solve the problem, report the build failure to the FreeBSD GNOME team at ${MAINTAINER}, and attach (a) \"${CONFIGURE_WRKSRC}/${CONFIGURE_LOG}\", (b) the output of the failed make command, and (c) the gnomelogalyzer output. Also, it might be a good idea to provide an overview of all packages installed on your system (i.e. an \`ls ${PKG_DBDIR}\`). Put your attachment up on any website, copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) with the attachment. Try to avoid sending any attachments to the mailing list (${MAINTAINER}), because attachments sent to FreeBSD mailing lists are usually discarded by the mailing list software."
.endif