Subject: Re: Consulting MAINTAINER before updating a package
To: None <>
From: Roland Illig <>
List: tech-pkg
Date: 06/19/2007 01:11:11
Greg Troxel wrote:
> "Julio M. Merino Vidal" <> writes:
>>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

pkglint can not only check variable assignments, it also knows about 
comments and much other stuff, so this is a lame excuse. :)

Just tell me what pkglint should check or add the code yourself. By the 
way, all my maintained packages have MAINTAINERSTYLE=weak.