From owner-freebsd-ports Thu Jun 5 16:47:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA14278 for ports-outgoing; Thu, 5 Jun 1997 16:47:06 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA14269; Thu, 5 Jun 1997 16:46:58 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (8.8.5/8.8.5) with ESMTP id TAA06115; Thu, 5 Jun 1997 19:46:51 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPN/970116) with ESMTP id TAA00538; Thu, 5 Jun 1997 19:46:50 -0400 (EDT) To: John Polstra cc: "Julian H. Stacey" , ports@freebsd.org, committers@freebsd.org From: "Gary Palmer" Subject: Re: ports/comms/hylafax In-reply-to: Your message of "Thu, 05 Jun 1997 09:06:47 PDT." <199706051606.JAA06183@austin.polstra.com> Date: Thu, 05 Jun 1997 19:46:50 -0400 Message-ID: <533.865554410@orion.webspan.net> Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ CC: snipped ] John Polstra wrote in message ID <199706051606.JAA06183@austin.polstra.com>: > I'm with Satoshi on this whole thing. I agree. Not only does Satoshi do a sterling job of maintaining an every growing headache that is called `the ports collection', he does so in his spare time. Unless Julian is willing to dedicate that ammount of time to maintaining the ports, I suggest he stops complaining about decisions made. > Also, while the port was not marked broken, it was indeed broken -- > the distfile doesn't exist on the master site. Not to put too fine > a point on it, but to me that weakens your claim of authority over > the port as its maintainer. Infact, given that Julian had been asked to upgrade the port at least once, and that the PR for the new port sat for so long in GNATS before Satoshi did anything, I'm not at all sure what all the fuss is about. If Julian spent half the time that he has now expended writing mails attacking Satoshi on his port, this would never have happened. Instead he chose to decline Satoshi's upgrade requests, and now when someone else presented us with a solution, he chooses to attack instead. Not the most productive use of his time, IMHO. > Finally, no matter what Satoshi does, he doesn't have any way I know > of to delete the old port from your 2.2.1 CD. Or the in-the-works 2.2.2 CD either, since at least one copy has gone off to replication already. Gary -- Gary Palmer Speaking for no-one other than himself FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info