Subject: Re: Consulting MAINTAINER before updating a package
To: Julio M. Merino Vidal <jmmv84@gmail.com>
From: Greg Troxel <gdt@ir.bbn.com>
List: tech-pkg
Date: 06/18/2007 16:10:56
--=-=-=
"Julio M. Merino Vidal" <jmmv84@gmail.com> writes:
>> MAINTAINERSTYLE=strong
>
> Why does this need to be a *variable*? Will it be of any use,
> anywhere in the pkgsrc infrastructure? If not it should be a comment
> as Johnny (IIRC) mentioned.
I don't know; probably not. (How is MAINTAINER used? If displayed on a
web page, this is almost as useful.) My thought is that if we are going
to agree on semantics and a have a limited set of codepoints, then the
information should be expressed in machine-parseable form to reduce
confusion and unneeded variability. A variable lets pkglint detect
values not in the enum, but I suppose slows down make. A commented
variable assignment seems fine in order to get the rigid semantics
without the
# MAINTAINERSTYLE=strong
--=-=-=
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (NetBSD)
iD8DBQFGdubQ+vesoDJhHiURArZKAKCtd5pCRHqdXPf+Xm6tSArp5cCKDgCgmcqR
HgDH7SN92p5RZK5xSTaerG4=
=lJql
-----END PGP SIGNATURE-----
--=-=-=--