From owner-freebsd-ports Thu Aug 30 1:27: 6 2001 Delivered-To: freebsd-ports@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 33F3837B403; Thu, 30 Aug 2001 01:27:01 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 15cNAz-000P91-00; Thu, 30 Aug 2001 10:27:49 +0200 From: Sheldon Hearn To: cjclark@alum.mit.edu Cc: Cy Schubert - ITSD Open Systems Group , ijliao@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: ports/29137: Brand New Tripwire-2.3.1 Port (fwd) In-reply-to: Your message of "Wed, 29 Aug 2001 23:07:12 MST." <20010829230711.H9807@blossom.cjclark.org> Date: Thu, 30 Aug 2001 10:27:49 +0200 Message-ID: <96658.999160069@axl.seasidesoftware.co.za> Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 29 Aug 2001 23:07:12 MST, "Crist J. Clark" wrote: > As long as the maintainers are still willing to keep them up, I don't > see any reason to remove them. Of course, if one of the maintainers > (you for example) no longer wish to support one, unless someone else > speaks up to support it, it should go. I think you're approaching this from the wrong angle. The default should be to update existing ports rather than spawn new ones. Special considerations may motivate you to add new ports (e.g. a new version of a package with an incompatible configuration file syntax), but that should never be the default. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message