From owner-freebsd-ports@FreeBSD.ORG Sat Feb 25 19:18:20 2012 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 C4514106564A for ; Sat, 25 Feb 2012 19:18:20 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4F3E88FC13 for ; Sat, 25 Feb 2012 19:18:19 +0000 (UTC) Received: by werm13 with SMTP id m13so3017988wer.13 for ; Sat, 25 Feb 2012 11:18:19 -0800 (PST) Received-SPF: pass (google.com: domain of kob6558@gmail.com designates 10.180.24.166 as permitted sender) client-ip=10.180.24.166; Authentication-Results: mr.google.com; spf=pass (google.com: domain of kob6558@gmail.com designates 10.180.24.166 as permitted sender) smtp.mail=kob6558@gmail.com; dkim=pass header.i=kob6558@gmail.com Received: from mr.google.com ([10.180.24.166]) by 10.180.24.166 with SMTP id v6mr5923516wif.10.1330197499387 (num_hops = 1); Sat, 25 Feb 2012 11:18:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=K89POO6P33lVB6gwu5Nt2pVOnfPoHNwWMjOhXceqtZU=; b=FCTnyOzc1/Lt/W/xMvc0JAPBUCAg8u+HS4IG4a3QadfTZg9L0wjsN6X1tyCkDjl+Jo fdhHpbbsj1JB5txiEVo5kaJgdkARK+wiH3vmsY9VZ7/CO2DflAtnb7EmyYP91vbLM68u 9JNTf7KltllG19EBG5wDlUo2peZl1FWZL1K+E= MIME-Version: 1.0 Received: by 10.180.24.166 with SMTP id v6mr4676098wif.10.1330197499163; Sat, 25 Feb 2012 11:18:19 -0800 (PST) Received: by 10.223.16.82 with HTTP; Sat, 25 Feb 2012 11:18:19 -0800 (PST) In-Reply-To: References: Date: Sat, 25 Feb 2012 11:18:19 -0800 Message-ID: From: Kevin Oberman To: Royce Williams Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org Subject: Re: portupgrade -> portmaster Rosetta Stone? 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: Sat, 25 Feb 2012 19:18:20 -0000 On Sat, Feb 25, 2012 at 10:21 AM, Royce Williams wrote: > I noticed that the portupgrade port got returned to ports@ with this note= : > > ports-mgmt/portupgrade > =A0- =A0Reassign to ports@ > =A0 =A0 please consider using ports-mgmt/portmaster > > =A0Discussed with: bugmeister(eadler, linimon), ruby(swills, pgollucci) v= ia > =A0#bsdports > =A022 Feb 2012 - pgollucci > =A0http://www.freshports.org/ports-mgmt/portupgrade/ > > > To ease the transition, does anyone know of a Rosetta Stone table, or > "portmaster for native speakers of portupgrade"? Many things are just the same, but thee are a few 'gotcha's to be aware of. 1. There is no 'force' option for portmaster. You tell it to re-install a port and it does so. 2. If a directory is not specified (e.g. graphics/Imagemagick), the arguments are globs so that 'portmaster mplayer' will also run on mplayer-skins or any other installed port starting with mplayer. (I find this annoying, but Doug said that he got lots of requests for this behavior.) 3. portmaster ALWAYS behaves like -R was specified. The -R option in portmaster is very useful in some cases, but it is completely different from portupgrade. It is for Restart and is useful when updating lots of ports at once. 4. By default, portmaster will ask if you want ot delete the old distfile after installing an upgrade that uses a newer distfile. -D prevents this so you can run as close to non-stop as is possible. If you use -D, you may want to run 'portmaster --clean-distfiles' when you are all done. (portupgrade never attempts to clean up old distfiles and expects you to run portsclean for this.) Read the man page! Really! portmaster(8) has examples that will greatly simplify big jobs like completely reinstalling your ports and will clarify some of portmaster's behavior. I find portmaster vastly superior to portupgrade and highly recommended it before portupgrade was deprecated, though it did take a little getting used to, often because some things were so close to the same as portupgrade. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com