Date: Tue, 5 Jan 1999 11:37:21 +0100 (MET) From: Luigi Rizzo <luigi@labinfo.iet.unipi.it> To: itojun@FreeBSD.ORG (Jun-ichiro Itoh) Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: ports/devel/portlint Makefile ports/devel/portlint/scripts Message-ID: <199901051037.LAA02324@labinfo.iet.unipi.it> In-Reply-To: <199901051223.EAA04049@freefall.freebsd.org> from "Jun-ichiro Itoh" at Jan 5, 99 04:23:10 am
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. Not this specific case (plus i cannot think of anything more appropriate than portlint for a place in the ports tree), bu This would be the case e.g. with a number of FreeBSD-only apps that do not find their place in the source tree and do not find a better home... 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. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901051037.LAA02324>