From owner-freebsd-ports@FreeBSD.ORG Thu Aug 20 15:19:30 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F4186106568E; Thu, 20 Aug 2009 15:19:29 +0000 (UTC) (envelope-from prvs=47659acf4=pschmehl_lists@tx.rr.com) Received: from ip-relay-002.utdallas.edu (ip-relay-002.utdallas.edu [129.110.20.112]) by mx1.freebsd.org (Postfix) with ESMTP id 74E018FC16; Thu, 20 Aug 2009 15:19:29 +0000 (UTC) X-Group: RELAYLIST X-IronPort-AV: E=Sophos;i="4.43,414,1246856400"; d="scan'208";a="15220083" Received: from smtp3.utdallas.edu ([129.110.20.110]) by ip-relay-002.utdallas.edu with ESMTP; 20 Aug 2009 09:50:18 -0500 Received: from utd65257.utdallas.edu (utd65257.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTPSA id A25C14EF48; Thu, 20 Aug 2009 09:50:18 -0500 (CDT) Date: Thu, 20 Aug 2009 14:50:18 +0000 From: Paul Schmehl To: "Philip M. Gollucci" , Dmitry Marakasov Message-ID: <6B974976DD234EF08949F6A8@utd65257.utdallas.edu> In-Reply-To: <4A8CCC24.8050605@p6m7g8.com> References: <20090820023314.GF1295@hades.panopticon> <4A8CCC24.8050605@p6m7g8.com> X-Mailer: Mulberry/4.0.6 (Linux/x86) X-Munged-Reply-To: Figure it out MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-ports@freebsd.org, portmgr@freebsd.org Subject: Re: Migration to new SourceForge url scheme now inevitable, solution X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2009 15:19:30 -0000 --On Wednesday, August 19, 2009 23:08:04 -0500 "Philip M. Gollucci" wrote: > > Dmitry Marakasov wrote: >> [1] http://people.freebsd.org/~amdmi3/sf.pl.txt > Awesome. > > Rewriting this: > my $portname = `make -VPORTNAME`; > chomp $portname; > my $portname_lc = lc($portname); > > my $portversion = `make -VPORTVERSION`; > chomp $portversion; > > Like this, will help substantially by reducing make spawns by 1/2, > you'll notice the ports tinderbox code does this too :) > > my @lines = lc `make -V PORTNAME -V PORTVERSION`; > my $portname = $lines[0]; chomp $portname; > my $portversion = $lines[1]; chomp $portversion; > > (untested) > >> [2] http://people.freebsd.org/~amdmi3/sourceforge-subdirs.txt >> [3] http://people.freebsd.org/~amdmi3/sourceforge-subdirs-top.txt I've been following this discussion closely since several of my ports fetch from Sourceforge. Is it safe to assume that some global solution will be applied to the ports tree? Or are we maintainers going to need to submit PRs for affected ports once a solution is agreed upon? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson