From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 02:57:09 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F304F106566C for ; Fri, 20 Jan 2012 02:57:09 +0000 (UTC) (envelope-from mwm@mired.org) Received: from mail-iy0-f196.google.com (mail-iy0-f196.google.com [209.85.210.196]) by mx1.freebsd.org (Postfix) with ESMTP id B5CA68FC0C for ; Fri, 20 Jan 2012 02:57:09 +0000 (UTC) Received: by iagz16 with SMTP id z16so33470iag.7 for ; Thu, 19 Jan 2012 18:57:09 -0800 (PST) Received: by 10.50.89.197 with SMTP id bq5mr30681912igb.24.1327028228050; Thu, 19 Jan 2012 18:57:08 -0800 (PST) Received: from bhuda.mired.org (173-164-244-209-SFBA.hfc.comcastbusiness.net. [173.164.244.209]) by mx.google.com with ESMTPS id or2sm41732891igc.5.2012.01.19.18.57.07 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 Jan 2012 18:57:07 -0800 (PST) Date: Thu, 19 Jan 2012 18:57:04 -0800 From: Mike Meyer To: freebsd-hackers@freebsd.org Message-ID: <20120119185704.268327ba@bhuda.mired.org> In-Reply-To: References: Organization: Meyer Consulting X-Mailer: Claws Mail 3.7.10 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEXguIzRkGnhyaz069mXhW0WHRnbrnR9WCQ6LB0CchNMAAACSUlEQVQ4jV2TQW7jMAxFGaPQOgQEdZaGMsgBrAvUA03dCxj1Uu4U2gfwQD7AGNax51NK07RcxXz6/CSl0Ij450vkPG1jzpIZM1UwDCl/xB14TWnNX8A00Qj5a0mnVFVbVUz4MeErea2HikSRqZzY894zwg9p2+/AtO8LzxFED+tNAUFeU29iFOLRxlZAcdo9A8wi8ZBMV4BKPde82Oxrvs6BTkulQIClte0DLFzzsKk9j1MBex8iUaP00Bd78S/muyFScrTXz6zLkEUxJp+SabQfNOs4f4Jpx5qSZ/304PWwlEWP1cOn/mJQR7EOD+uKhjcBLziuL7xoY5Xm+VFAUSw/LwwwsHEHxihpwV4EJH0xXRkbw1PkRw+X4pEuSJwBggqk+HEYKkiL5/74/nQkogigzQsAFrakxZyfw3wMIEEZPv4AWMfxwqE5GNxGaERjmH+PG8AE0L4/w9g0lsp1raLYAN5azQa+AOoO9NwcpFkTrG2VKNMNEL5UKUUAw34tha0z7onUG0oBoNtczE04GwFE3wCHc0ChezAJ6A1WMV81AtY7wDAJSlXwV+4cwBvsOsrQMRawfQEBz0deEZ7WNpV2szckIKo5VpDHDSDvF1GItwqqAlG01Hh50BGtVhuUkjkasg/14bYFGCgWg1fSWHvmOoJck2xdp9ZvZBHzDVTzX23TkrOn7qe5U2COEw5D4Vx3qEQpFY2Z/3QFnJxzp7YCmSMG19nOUoe869zZfOQb5ywQuWu0yCn5+8gxZz+BE7vG3j4/wbf4D/sXN9Wug1s7AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD has serious problems with focus, longevity, and lifecycle X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 02:57:10 -0000 On Thu, 19 Jan 2012 08:07:43 +0100 vermaden wrote: > I got these maintainers email addresses from http://freshports.org > page, are they up-to-date there? Maybe that is the problem and > that my mails jest went to /dev/null ... Just checking for sure. I dunno. If you want the maintainer as of your update of the ports tree, go to the port and do "make -V MAINTAINER". I've generally had good luck with ports. I ran for years with LOCALBASE set to /usr/opt (what can I say, I was a masochist). I'd regularly find ports that failed to build under those conditions. I'd try and patch the port to fix it, or sometimes just kludge it to work, then mail the maintainer with the patch. Most of them fixed things pretty quickly. Ditto after the conversion to rc.d - I'd find ports that needed such scripts, write them, and send them to the maintainer. There, my patches weren't accepted as is quite so often, but I generally saw an appropriate script (even if inferior to mine :-) fairly quickly. And as a port maintainer, I tried to respond quickly to such requests. Getting patches accepted was a spottier story. It generally worked better if I approached the maintainer with "I'd like to fix this/add this feature, are you interested" than just submitting patches to gnats. http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org