From owner-freebsd-ports  Fri Feb  4 16:40:48 2000
Delivered-To: freebsd-ports@freebsd.org
Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7])
	by builder.freebsd.org (Postfix) with ESMTP
	id 4CAC7449E; Fri,  4 Feb 2000 16:40:41 -0800 (PST)
Received: (from archie@localhost)
	by bubba.whistle.com (8.9.2/8.9.2) id QAA16328;
	Fri, 4 Feb 2000 16:40:57 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <200002050040.QAA16328@bubba.whistle.com>
Subject: Re: need help with portlint
In-Reply-To: <20000204160509.B57320@dragon.nuxi.com> from "David O'Brien" at "Feb 4, 2000 04:05:09 pm"
To: obrien@FreeBSD.ORG
Date: Fri, 4 Feb 2000 16:40:57 -0800 (PST)
Cc: mharo@area51.fremont.ca.us, freebsd-ports@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

David O'Brien writes:
> > My only complaint is that it seems to get confused by blank lines.
> > First, what's so bad about blank lines?  They help make the Makefile
> > readable.
> 
> In general I agree blank lines *can* make a Makefile more readable.  But
> sometimes not.  The Ports Team has come up with a strick style format
> that we would preferred was followed.  It may not always be the best, but
> in the end it just makes things much more consistent -- a trademark of
> FreeBSD/BSD vs. the others.

That sounds reasonable.. so in this case, portlint should say
something like "you got too many blank lines", etc.

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message