From owner-freebsd-ports-bugs@FreeBSD.ORG Thu May 4 14:10:16 2006 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA3CB16A423 for ; Thu, 4 May 2006 14:10:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 981BE43D46 for ; Thu, 4 May 2006 14:10:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k44EAGOG063334 for ; Thu, 4 May 2006 14:10:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k44EAGtq063333; Thu, 4 May 2006 14:10:16 GMT (envelope-from gnats) Date: Thu, 4 May 2006 14:10:16 GMT Message-Id: <200605041410.k44EAGtq063333@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: "Andrew Pantyukhin" Cc: Subject: Re: ports/96764: new port: www/xpi-cutemenus_-_crystal_svg X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrew Pantyukhin List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 14:10:16 -0000 The following reply was made to PR ports/96764; it has been noted by GNATS. From: "Andrew Pantyukhin" To: "Lapo Luchini" Cc: bug-followup@freebsd.org Subject: Re: ports/96764: new port: www/xpi-cutemenus_-_crystal_svg Date: Thu, 4 May 2006 18:07:38 +0400 On 5/4/06, Lapo Luchini wrote: > I agree, it seemed a bit ugly to me as well, but didn't really think > about it. > I will rename and test it again later, or possibly tomorrow. I don't think there's need for additional testing unless a committer requests it. Most likely he'll handle dirname change all by himself. If you want to change portname, too, then, indeed, you should test you port again and submit a new shar.