From owner-freebsd-ports@FreeBSD.ORG Sat Jun 7 20:22:52 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 575E6AFA for ; Sat, 7 Jun 2014 20:22:52 +0000 (UTC) Received: from spectrum.skysmurf.nl (spectrum.skysmurf.nl [82.95.125.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BFED42ECD for ; Sat, 7 Jun 2014 20:22:51 +0000 (UTC) Received: from spectrum.skysmurf.nl (mail.skysmurf.nl [192.168.42.4] (may be forged)) by spectrum.skysmurf.nl (8.14.7/8.14.7) with SMTP id s57KMfXv059705; Sat, 7 Jun 2014 22:22:41 +0200 (CEST) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Sat, 07 Jun 2014 22:22:41 +0200 Date: Sat, 7 Jun 2014 22:22:41 +0200 From: "A.J. 'Fonz' van Werven" To: Paul Schmehl Subject: Re: How are ports built now Message-ID: <20140607202241.GA59544@spectrum.skysmurf.nl> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.5.23 (2014-03-12) Cc: FreeBSD Ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jun 2014 20:22:52 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Paul Schmehl wrote: > Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] > Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. > Now, when I run portmaster -ad, it seems to keep reinstalling the same > ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? > Are we forced to now go to binary packages only? No, of course not. However, it might be that Portmaster cannot handle *installing* binary packages in the new format. I'm not sure because I let Portmaster build PKGNG-style binary packages and use PKGNG to install those on other jails/systems, but I seem to recall something along the lines of Portmaster not yet being able to use PKGNG-style binary package repositories. I might be way off here, though. AvW --=20 I'm not completely useless, I can be used as a bad example. --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJTk3SRAAoJEAfP7gJTaCe8KEIQANbnGTNJdqLH2cuhPP2WRK/q PrvJvsOL+pva791r1+pPj5U6WZcemVZ2P1GM5h3fim0Q8PKNDTFLZUgnivfgNumD dkil1r+IRctJhdeiILIL3UtS/x0XWMKpMNJJbuAmkSIojJdMyhcRup4GLsxEhD9+ V+8AsJjB+v+HoAg7/Vh0yQoXg4DkW5fxrZmbIlrd5nJFCeD/yuqmc/ljltWrzskh Bkkju8ihn1IB0ms4oUNqqqo1NDOTMFtpNJlpm6eBUwsxH/GB64RKpgRsLCEmRCGB vMI6Kcw0k78Qsa8FF0rMDVkRmOLEpPhrLI308mjNw7RcEP5X6F/oFwXG4iKfK5b8 vEy2AzYwCIeO4cCcoRTelcPOnBp6CKCDBCsExB+vctUh378+9pRoMCvV4vVSYwAj n5pQvA5n99Uyicry/hd/qNsESUb0RDlik7HTntcdtzdzW3IctHtFNK/qiwGYLMN8 M/4+ac74rm30E8ARTJNe1L9Y7F4f3Rx87R2rJU6n8I34mP7b+xPTiNq/5P4ec18v DKHC0NMh/O5sZaWPFTiUDa0Q1i4NUlnrwSJRrv1tXZKuvRo09WE/nMR6pgEsU47r aOpFRwjlniUVYzIxX83hAAFr3e973vwNI0hq1S0HG/o0Yw7A49LgLLQehuHvn8AW Sgz2uX1zCE62MeBibhSV =8Wko -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24--