From owner-cvs-ports  Tue Apr 18 03:10:11 1995
Return-Path: cvs-ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id DAA28809
          for cvs-ports-outgoing; Tue, 18 Apr 1995 03:10:11 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA28797
          ; Tue, 18 Apr 1995 03:09:59 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.9/8.6.9) id DAA03734; Tue, 18 Apr 1995 03:09:56 -0700
Date: Tue, 18 Apr 1995 03:09:56 -0700
Message-Id: <199504181009.DAA03734@silvia.HIP.Berkeley.EDU>
To: jkh@freefall.cdrom.com
CC: phk@ref.tfs.com, pst@shockwave.com, CVS-commiters@freefall.cdrom.com,
        cvs-ports@freefall.cdrom.com
In-reply-to: <4767.798164423@freefall.cdrom.com> (jkh@freefall.cdrom.com)
Subject: Re: cvs commit: ports/net/cern_linemode - Imported sources
From: asami@cs.berkeley.edu (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=)
Sender: cvs-ports-owner@freebsd.org
Precedence: bulk

 * Either that or indicative of the fact that the porter simply has too
 * much time on their hands.  Truly, by that yardstick you could justify
 * *anything*!  I think Paul's right - some degree of quality control
 * must be instituted before we wind up with potentially hundreds of
 * mutant and broken ports which make the entire collection smell like
 * a leper colony on a hot day.
 * 
 * In any case, this isn't our call.  It's Satoshi's.  He's the portsmeister
 * and the guy who ends up CLEANING UP the messes the rest of the porters
 * leave behind, so if he says "no" to something then it means "NO".

Gee thanks, I feel like a king and a janitor at the same time! ;)

Anyway, I don't mind anything as long as

(1) It doesn't do something it shouldn't.  Running ldconfig, changing
    permissions of /var/mail, etc., are not something a port should
    do, at least without the user's consent.

(2) It comes with the correct package files, and

(3) Somebody is willing to assume the responsibility of maintaining
    the port so that I can do a periodic top-down build and bounce the
    error messages to that person.  That's why I'm yelling to people
    to add the MAINTAINER line!  Maybe I should go in and delete all
    the ports without a MAINTAINER! :)

I make no judgement to the feasability of the software itself.  I
don't have time to do that anyway.  If it's really reeeeeeeeally bad
that we receive many complaints, we can talk.

Satoshi