From owner-freebsd-doc@FreeBSD.ORG Fri May 31 07:37:55 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CE274279 for ; Fri, 31 May 2013 07:37:55 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id A54F7A9D for ; Fri, 31 May 2013 07:37:55 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id a14so3177740iee.27 for ; Fri, 31 May 2013 00:37:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=dkf925q408Dm4oMMpTzq7+I1cKJKnUerU9V90w//m9s=; b=JTA9rmf4k+mHTHoFvlx6TqN/UDatnPp3Z7DrteN20vcsg4F6KM78UPWyLX8UU39yy9 B9WlxclmYeCRGtoMgJh0zyuzI/jbC2Uy9qJMAivsv9ZIujzEesvI0cMrcfDIvur+O5ig DAD31Mx9cP6Aef9I4Qd0FcMTZqxWCJqlikQSb1yL52xmZASSA5dvtF4E9wBZvOIIkKQV Qw7WpSneOGVBNpWJpNQlM5R6Tg+UCnO7PrwXjO6Axbu/aYsHFUH4Qe0j73sfIosvC9IZ wbpCelcn+ccIs2gX5/CXwKLo8hLGHKFuXiWtzttY/HQfB1F8rADitZzt12IyvGkaJsXY u+uw== X-Received: by 10.50.153.113 with SMTP id vf17mr1044739igb.101.1369985875348; Fri, 31 May 2013 00:37:55 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.64.71.101 with HTTP; Fri, 31 May 2013 00:37:24 -0700 (PDT) In-Reply-To: <201305310706.r4V76uKC001292@chilled.skew.org> References: <201305310706.r4V76uKC001292@chilled.skew.org> From: Chris Rees Date: Fri, 31 May 2013 08:37:24 +0100 X-Google-Sender-Auth: KpQ7gQNmD114fLuiytI6vEVjX40 Message-ID: Subject: Re: Handbook suggestion: Dealing with Moved Ports To: Mike Brown Content-Type: text/plain; charset=ISO-8859-1 Cc: FBSD Doc project X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 07:37:55 -0000 On 31 May 2013 08:06, Mike Brown wrote: > [ This is a followup to my thread at http://lists.freebsd.org/pipermail/freebsd-ports/2013-May/083943.html ] > > /usr/ports/UPDATING does not normally mention when ports are moved. Unless > there are special considerations, that info only lives in /usr/ports/MOVED, > which isn't really something people are expected to look at. Rather, I think > people usually find out that a port has moved when they try to update their > installation of it and portmaster (or whatever) aborts with a message about > the situation: > > # portmaster www/mediawiki > > ===>>> The www/mediawiki port moved to www/mediawiki119 > ===>>> Reason: Rename mediawiki to mediawiki119 > > ===>>> Exiting > > ===>>> The second argument to -o can be a port in /var/db/pkg, > or a port directory from /usr/ports > > does not seem to be installed, > or listed as a dependency > > ===>>> No valid installed port, or port directory given > ===>>> Try portmaster --help > > ===>>> Killing background jobs > Terminated > ===>>> Exiting > > > As you can see, this is a rather cryptic message. What am I expected to do > here, in order to get this port upgraded? > > As far as I can tell, there's nothing about this in the Handbook, and the > message from portmaster isn't giving me any real guidance as to how to deal > with this situation. > > Perhaps ch. 5.8 - "Dealing with Broken Ports" could be followed by a chapter > on dealing with moved ports. I believe the proper course of action for people > in this situation is to first check /usr/ports/UPDATING for specific > instructions. If there are none, then it depends on what tool they're using. > For example, in my situation, I should do this: > > portmaster -o www/mediawiki-119 www/mediawiki > > or, if I want to upgrade to the newer version, I could instead do this: > > portmaster -o www/mediawiki-120 www/mediawiki > > I don't know what instructions should be for the other port/package systems; > I'm only using portmaster these days. Personally I put a note in UPDATING if it's a version switch, because these shouldn't normally be done automatically. Normally it's a case of: MOVED:cat/oldport|cat/newport|.... which causes the port to be replaced without question, which probably isn't desirable when you have to migrate configuration etc. That's when I put notes in UPDATING. Anyone disagree with me, or shall I document that? :) > (Also, unrelated: I suggest changing the first sentence of ch. 5.8 from > "If you come across a port that does not compile" > to > "If you come across a port that does not build or install properly".) Great idea, I'll do that. Chris