From owner-cvs-all  Tue Jan  5 06:15:06 1999
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA18794
          for cvs-all-outgoing; Tue, 5 Jan 1999 06:15:06 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18777;
          Tue, 5 Jan 1999 06:15:01 -0800 (PST)
          (envelope-from itojun@itojun.org)
Received: from kiwi.itojun.org (itojun@localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.1+3.1W/3.7W) with ESMTP id XAA17843;
	Tue, 5 Jan 1999 23:13:36 +0900 (JST)
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
In-reply-to: luigi's message of Tue, 05 Jan 1999 11:37:21 +0100.
      <199901051037.LAA02324@labinfo.iet.unipi.it> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: cvs commit: ports/devel/portlint Makefile ports/devel/portlint/scripts 
From: Jun-ichiro itojun Hagino <itojun@iijlab.net>
Date: Tue, 05 Jan 1999 23:13:35 +0900
Message-ID: <17839.915545615@coconut.itojun.org>
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk


>>   Added files:
>>     devel/portlint/scripts configure 
>>     devel/portlint/src   portlint.1 portlint.pl 
>>   Log:
>>   being tired of maintaining portlint only by myself, I decided to
>>   put the source code for "portlint" into FreeBSD port tree.  The
>I think this approach (having sources into the FreeBSD ports tree)
>is useful because it lets people share&maintain code more easily;
>on the other hand it opens the door to a huge increase in the
>size/#ports ration of the ports tree.

	I did this by suggestion from asami-san.  I took the style from
	ports/benchmark/tcpblast, which has single C source code in
	ports/benchmark/tcpblast/src.

	I agree that this approach is not always recommended.

>I wonder if it wouldn't be the case to put portlint into the main
>source tree since it is a useful tool and a small one.

	I have no opinion about the location.  My only concern is that portlint
	MUST be kept portable enough to support (Net|Open)BSD bsd.port.mk too.
	There are (Net|Open)BSD guys using portlint.

itojun

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