From owner-freebsd-ports Sat Apr 13 14:32:21 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA29460 for ports-outgoing; Sat, 13 Apr 1996 14:32:21 -0700 (PDT) Received: from maui.com (root@waena.mrtc.maui.com [199.4.33.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA29453 for ; Sat, 13 Apr 1996 14:32:16 -0700 (PDT) Received: from caliban.dihelix.com (caliban.dihelix.com [199.4.33.251]) by maui.com (8.6.10/8.6.6) with ESMTP id LAA16305; Sat, 13 Apr 1996 11:32:26 -1000 Received: (from langfod@localhost) by caliban.dihelix.com (8.7.5/8.6.9) id LAA27776; Sat, 13 Apr 1996 11:32:12 -1000 (HST) Message-Id: <199604132132.LAA27776@caliban.dihelix.com> Subject: Re: knews port uploaded To: andreas@knobel.gun.de (Andreas Klemm) Date: Sat, 13 Apr 1996 11:32:12 -1000 (HST) From: "David Langford" Cc: joerg_wunsch@uriah.heep.sax.de, mike@binghamton.edu, ports@freebsd.org In-Reply-To: from "Andreas Klemm" at Apr 13, 96 07:02:06 pm From: "David Langford" X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> > > > knews-0.9.6.port.tgz has been placed in >> > > > ftp://ftp.freebsd.org/pub/FreeBSD/incoming/ >> > > >> > > But you're aware that knews is already in the ports? It's still at >> > > version 0.9.3 there, but i assume that's not a big deal. > >Everybody is happy, if the hard f****** work gets done and if we >have a nice and up to date ports collection. But only the maintainer >should maintain a port, because he is the maintainer. > >Sounds logically, or ?! ;-)) >andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH So you are saying that when a port is three (3) versions behind and users would like an up-to-date version that they should just twiddle their thumbs waiting for some MAINTANER to come out of the woodwork instead of jumping in and helping everyone involved? I thought that this was one of the reasons that an incoming directory exsited at all. In this case (none of this is meant as any sort of flame BTW) that maintainer of the package (IMHO) should take the code in the incoming directory, check it out and see that it meets the ports standards and that standards set in any previous port of the package and then send in that port to the ports maintainer (i.e. Satoshi, i believe). (then a thank you note to the new version porter for the hard work and the work that they save the port maintainer.) This makes it so the a "port maintainer" is the helping hand to the "ports maintainer" (whew) and not the "Hey that MY program, hands off") Sounds logical to me. (Again this is not meant as a flame to anyone or of anything said- examples used for discussion purposes. As one who has ever sent in a port I am in no position to flame :) -David Langford langfod@dihelix.com FreeBSD caliban 2.2-CURRENT FreeBSD 2.2-CURRENT #0: Fri Apr 12 08:12:34 HST 1996 langfod@caliban:/usr/src/sys/compile/CALIBAN i386