pkg/50917: Better tagging of pkgsrc messages

[paul%whooppee.com@localhost]

>Number:         50917
>Category:       pkg
>Synopsis:       Better tagging of pkgsrc build messages
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 09 01:00:00 +0000 2016
>Originator:     Paul Goyette
>Release:        NetBSD 7.99.26
>Organization:
+------------------+--------------------------+------------------------+
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:      |
| (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com   |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
+------------------+--------------------------+------------------------+
>Environment:
	
	
System: NetBSD pokey.whooppee.com 7.99.26 NetBSD 7.99.26 (POKEY 2016-02-16 03:01:55) #0: Tue Feb 16 12:33:45 PHT 2016 paul%pokey.whooppee.com@localhost:/build/netbsd-local/obj/amd64/sys/arch/amd64/compile/POKEY amd64
Architecture: x86_64
Machine: amd64
>Description:
	Currently, pkgsrc build/install messages are preceeded with and
	followed by a line of ~75 equal signs.  Unfortunately, this tag
	occassionally occurs in output generated by some packages' native
	build procedures.  If one is building a number of packages, it's
	fairly easy to miss messages similar to

		The following files should be created for nas-1.9.4:

		/etc/rc.d/nasd (m=0755)
		    [/usr/pkg/share/examples/rc.d/nasd]

	Since the equal-sign line is fairly common tag, grep doesn't do
	a very good job of identifying these messages.

	Note that displaying of the $package/MESSAGE file doesn't suffer
	from this problem, since the $NetBSD$ id tag line is actually
	displayed (as part of the file contents).  It would  be useful
	if some other similar unique tag could be used for the above
	class of messages.
	
>How-To-Repeat:
	
>Fix:
	

>Unformatted: