From owner-freebsd-questions@FreeBSD.ORG Fri Jun 26 00:02:43 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A54A106564A for ; Fri, 26 Jun 2009 00:02:43 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-ew0-f213.google.com (mail-ew0-f213.google.com [209.85.219.213]) by mx1.freebsd.org (Postfix) with ESMTP id E57778FC1A for ; Fri, 26 Jun 2009 00:02:42 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by ewy9 with SMTP id 9so1408761ewy.43 for ; Thu, 25 Jun 2009 17:02:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type:content-transfer-encoding; bh=5ONAcZFp7xMR9QO4J7Lo3Vnls+Dugc6aAnWAbqLCUC4=; b=LVGJIhiAVvKhtaKs2wx6dykHcIAmfgcBUfH0HI3vqzu+7GBvUbQop0LLvutr7WWFT2 Xglk27mqxdcudtmLQ7P2zcS+oTI+/ezZkq8Lcbo/3O9NmUWfpRgjV60PZdrVZIn2lgLC o8KvZtpwEltpX07tgFuE19EGQTQ16b2NJNd8Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; b=GF1saw7k8lgEymf4VX2NK3nVJ/69Z9HYVBhgYkxJI3fWx6il4ClyOQaSS9a2/Lp7xG QJVSHZAiQJSc2pNB+73P/441YzV8g0mYIYb4zQKFwofRZiomh7qx+CZtSwAe+bnlC2Ok xh+1026wsAwF2MQfOd0QAKQj7KMARMK1Cng7s= Received: by 10.210.62.3 with SMTP id k3mr1070946eba.47.1245974562059; Thu, 25 Jun 2009 17:02:42 -0700 (PDT) Received: from gumby.homeunix.com (bb-87-81-140-128.ukonline.co.uk [87.81.140.128]) by mx.google.com with ESMTPS id 7sm721164eyg.2.2009.06.25.17.02.40 (version=SSLv3 cipher=RC4-MD5); Thu, 25 Jun 2009 17:02:41 -0700 (PDT) Date: Fri, 26 Jun 2009 01:02:38 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20090626010238.525398b6@gumby.homeunix.com> In-Reply-To: <4A43CDEC.7050602@onetel.com> References: <200906212038.39370.meslists@yahoo.fr> <4A3FE271.8080201@onetel.com> <20090622214802.0761813e@gumby.homeunix.com> <4A414751.9090804@onetel.com> <20090624015051.2ee23577@gumby.homeunix.com> <4A43CDEC.7050602@onetel.com> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.2; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: upgrading installed ports: time to do it ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2009 00:02:43 -0000 On Thu, 25 Jun 2009 20:20:12 +0100 Chris Whitehouse wrote: > RW wrote: > > Portmanger does cope with most of the "portupgrade -o" and > > "portupgrade -r" entries, although sometime it will need to be run > > (or rerun) in pristine-mode. > > just curious, do you know this because you know how they all work or > have you tried them. And how does portmaster fit in? Does it use the > same 'leaf-nodes first' algorithm as portmanager? It's leaf-last, the leaves are on the top of the tree. All the upgrade tools build in dependency order, but portmanager also rebuilds ports that directly depend on the ports it's upgraded (originally it included indirect dependencies, but that's now only done in pristine mode). In other words it, more or less, does the equivalent of "portupgrade -fr" as a matter of course. As regards "portupgrade -o", it depends on the circumstances. In the case of perl5.8 to perl5.10, I would expect that it would continue with perl5.8 until something actually needs perl5.10. It would then detect a conflict, remove perl5.8, install perl5.10 and then rebuild everything that depended on perl5.8. Essentially it would do the right thing. I'm not sure about python, it's bit more complicated, but I would guess it would be similar to perl.