From owner-freebsd-ports@FreeBSD.ORG Fri Jul 28 14:27:14 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F41FA16A4DA for ; Fri, 28 Jul 2006 14:27:13 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from rwcrmhc15.comcast.net (rwcrmhc15.comcast.net [204.127.192.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92BB443D5A for ; Fri, 28 Jul 2006 14:27:13 +0000 (GMT) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-24-6-181-195.hsd1.ca.comcast.net[24.6.181.195]) by comcast.net (rwcrmhc15) with ESMTP id <20060728142211m1500dum7he>; Fri, 28 Jul 2006 14:22:11 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 4F4965C03F; Fri, 28 Jul 2006 07:22:07 -0700 (PDT) Date: Fri, 28 Jul 2006 07:22:07 -0700 From: Jeremy Chadwick To: Rico Secada Message-ID: <20060728142207.GA63921@icarus.home.lan> Mail-Followup-To: Rico Secada , freebsd-ports@freebsd.org References: <20060728155658.49f49598@dansknet.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060728155658.49f49598@dansknet.dk> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-ports@freebsd.org Subject: Re: GNAT port is broken, maintainer don't care X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 14:27:14 -0000 On Fri, Jul 28, 2006 at 03:56:58PM +0200, Rico Secada wrote: > Simply put: "I am a maintainer of a port on FreeBSD, but I only have time to run current, and thus doesn't care a rats ass about if the port works on RELEASE, eventhough thats the most widely used version of FreeBSD." > > This can't be right! You have to remember that with ports, it's at the discretion of the port author to test his/her port on different architectures and different setups. That said... The port is his responsibility: *PERIOD*. If he doesn't want the responsibility of testing his work on non-CURRENT releases, then he should either 1) find someone who can test it for him that doesn't use CURENT, or 2) step down from maintaining the port. In his defence, there is still the chance that all of your machines that you maintain are misconfigured. I don't care if you have a thousand of them -- if they're all poorly maintained or improperly managed (such as not using mergemaster, not following installworld procedures per /usr/src/Makefile step-by-step, not following UPDATING changes, etc.), then it wouldn't be the fault of the port maintainer. I have seen entire clusters of FreeBSD machines incorrectly maintained before, where the admins were absolutely BOFH-ish with their opinion that "they were being managed right". I'm not saying that's the case here -- so please don't take it personally -- but it's something to take into consideration before passing judgement. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |