From owner-freebsd-ports@FreeBSD.ORG Mon Dec 24 01:25:37 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3BB7CB75 for ; Mon, 24 Dec 2012 01:25:37 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by mx1.freebsd.org (Postfix) with ESMTP id AD94D8FC15 for ; Mon, 24 Dec 2012 01:25:36 +0000 (UTC) Received: by mail-ea0-f172.google.com with SMTP id a1so2660756eaa.17 for ; Sun, 23 Dec 2012 17:25:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=m1Wfbcae/6gaC4SFefM5DSGPoJVmPvKEgzDnkLwAbM4=; b=qoRYCXu8tYvfELHxJG/Wd3G/r2jgisiQDH1LBuvbjQC2s/TYBGl/F14VFTohFBSf/N R+NUWqCzdaiuAg+l8MqB+Fp7RWtKf6SHMTEhpLKqvehX5wexjI53QqrREGYtNszNsrRX WLKRYeZDJVEEwUBdM3USEEPcyoynF2b9Fjz0kwrw0VbxLiXK8V8VVPlJAhFIU8uxoLCP 0t+cvctG/ectA59BHSn1ETVNfTEyY96I1KwoRLUalCQuPTGH2eybiBii2JPhkOI93xX1 AJ50QujKeRydKEWSSiibydb9h8JVPJgDwNRkGuRdirIWxIaf1fIrHDPJ51JtPfHMXHdF t46A== X-Received: by 10.14.176.66 with SMTP id a42mr51550513eem.34.1356312329937; Sun, 23 Dec 2012 17:25:29 -0800 (PST) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPS id v46sm38106300eep.1.2012.12.23.17.25.29 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 23 Dec 2012 17:25:29 -0800 (PST) Sender: Baptiste Daroussin Date: Mon, 24 Dec 2012 02:25:27 +0100 From: Baptiste Daroussin To: freebsd-ports@freebsd.org Subject: Re: Upgrading ports problem with portupgrade(pkgng) Message-ID: <20121224012527.GF42913@ithaqua.etoilebsd.net> References: <50D779F6.4080407@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="V4b9U9vrdWczvw78" Content-Disposition: inline In-Reply-To: <50D779F6.4080407@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2012 01:25:37 -0000 --V4b9U9vrdWczvw78 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 23, 2012 at 09:39:02PM +0000, Matthew Seaman wrote: > On 23/12/2012 21:05, Beach Geek wrote: > > And as I understand, poudriere must be used instead of portupgrade to > > create packages? >=20 > That's not right. >=20 > poudriere is an offline pkg building system, designed to build > packages in a sandbox, and then create a pkgng repository accessible > to various client machines. You can use it locally to maintain a > single machine, but that's sort of missing the point. It only works > with pkgng, although I believe you can run it on a non-pkgng machine > to create a repo for maintaining other pkgng-enabled machines. Last part is not entirely true, poudriere can work work both pkgng and pkg_install it is not pkgng only. yes it can run on a non-pkgng machine, bu= t it still needs pkgng to be install on the host (installed not necessary used).= and it can work on a pkgng machine to build pkg_install packages without the ne= ed of the pkg_install tools on the host. It can also be used to maintain a single machine, by creating the repositor= y of packages and once done you can simply install/upgrade them using pkgng. It = is very convenient, and easy to do, because it is fast (poudriere is heavily parallelized) it allows the users to really upgrade things when they all su= cceed at building, meaning your system is always safe. It allows you to allows be= png or pcre upgrade proof, because such upgrade will be detected by poudriere without the need of a bump in portrevision. If the user end up with a missi= ng libpcre.so.1 a simple pkg install -fR pcre will fix the situation almost immediatly. >=20 > portmaster and portupgrade cover basically the same territory. > They're designed to maintain the locally installed package set on a > machine. To that end, both of them are wrappers around the ports, > and facilitate installing packages by compiling the relevant port > source code. The can also use binary packages, typically from a > FreeBSD ftp server. Initially they used pkg_tools packages, but > both have been modified to work with pkgng packages as well. >=20 > pkgng is a package registry application and a binary package > manager. It doesn't understand the ports. However, if you have > access to a suitable source of pre-compiled packages you can use > just pkgng to manage those, and have no need for portmaster or > portupgrade. poudriere is intended to provide that 'suitable > source.' although once the official pkg build cluster gets up and > running, users should be able to use that instead. >=20 > Cheers. >=20 > Matthew >=20 regards, Bapt --V4b9U9vrdWczvw78 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlDXrwcACgkQ8kTtMUmk6EwcGgCgnxubzRY6SNsLsjnYQWSd1yr3 gkMAn1kQF1yOz+GurN01rdbeo7aaESrk =UdGW -----END PGP SIGNATURE----- --V4b9U9vrdWczvw78--