From owner-freebsd-ports@FreeBSD.ORG Thu Mar 15 21:46:31 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AF47F1065673 for ; Thu, 15 Mar 2012 21:46:31 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 951068FC17 for ; Thu, 15 Mar 2012 21:46:31 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id C3E5450827 for ; Thu, 15 Mar 2012 14:46:23 -0700 (PDT) To: ports@freebsd.org Date: Thu, 15 Mar 2012 14:46:23 -0700 Message-ID: <86781.1331847983@tristatelogic.com> From: "Ronald F. Guilmette" Cc: Subject: graphics/dri maintainer? 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: Thu, 15 Mar 2012 21:46:31 -0000 Who is allegedly maintaining the graphics/dri port at this moment in time? I would rather like to know, because it is in serious need of updating. (The version upon which the port was based was apparently released on June 23, 2009, and there have been numerous new releases since then.) I wouldn't care, except that gthumb was crashing on me (SIGSEGV) and a stack backtrace clearly showed that the problem resides within the Mesa/DRI library. Of course, I asked the Mesa/DRI dudes for help and advice, and of course they suggested that I consider using a rather more current version.