From owner-freebsd-ports@FreeBSD.ORG Tue Mar 15 11:56:51 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B5611065672; Tue, 15 Mar 2011 11:56:51 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from unimail.uni-dortmund.de (mx1.HRZ.Uni-Dortmund.DE [129.217.128.51]) by mx1.freebsd.org (Postfix) with ESMTP id 986FE8FC13; Tue, 15 Mar 2011 11:56:50 +0000 (UTC) Received: from [192.168.178.26] (dtmd-4db7a291.pool.mediaWays.net [77.183.162.145]) (authenticated bits=0) by unimail.uni-dortmund.de (8.14.4/8.14.4) with ESMTP id p2FBIvbD023714 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 15 Mar 2011 12:18:57 +0100 (CET) Message-ID: <4D7F4B22.6020403@FreeBSD.org> Date: Tue, 15 Mar 2011 12:18:58 +0100 From: Matthias Andree Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.15) Gecko/20110303 Mnenhy/0.8.3 Thunderbird/3.1.9 MIME-Version: 1.0 To: Wesley Shields References: <20110314003535.GC5392@server.vk2pj.dyndns.org> <4D7D653A.6090703@dougbarton.us> <20110314131946.GA37317@atarininja.org> In-Reply-To: <20110314131946.GA37317@atarininja.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, "J. Hellenthal" , Doug Barton , Peter Jeremy Subject: site-packages upgrades (was: portmaster comments) 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: Tue, 15 Mar 2011 11:56:51 -0000 Am 14.03.2011 14:19, schrieb Wesley Shields: >> This doesn't have any effect for, >> /usr/ports/lang/python/Makefile:31:.if defined(USE_PORTMASTER) >> >> Does it ? > > It has an effect on how the upgrade-site-packages target works. I wrote > it specifically because I didn't want to have to install portupgrade > just to get the upgrade-site-packages target to work. Oh, if I may add a shameless plug here, I'd like to advertise ports-mgmt/pkgs_which that I've written partially out of the same motivation (get upgrade-site-packages targets working without portupgrade or pkg_which) and efficiently. Basically you can do pkgs_which -qo /usr/local/lib/python2.6 to get a list of packages that need upgrading (takes < 10 s for a dual-core energy-efficient 2 GHz-class computer with somewhat slow disks and UFS) or portmaster -d $(pkgs_which -qo /usr/local/lib/python2.6) to upgrade them all. Yeah, this code should've been written much sooner, and I've been having this idea for a while, but now it's there. > I think you might be confusing two different issues. The USE_PORTMASTER > knob was put in place specifically for the upgrade-site-packages target, > which is not something called during the normal build process by any > upgrading tool. I'm not sure how using UPGRADE_TOOL will help this at > all. Possibly not at all -- it would possibly be more useful to standardize these "post-upgrade" jobs. One "post-install" for the regular stuff, and one "post-nontrivial-upgrade" (for want of a better name) for the 2.6->2.7 or Perl 5.10->5.12 migration pains. -- Matthias Andree ports committer