From owner-freebsd-ports@FreeBSD.ORG Thu Feb 21 18:42:49 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E0AAA1A3 for ; Thu, 21 Feb 2013 18:42:49 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from rush.bluerosetech.com (rush.bluerosetech.com [IPv6:2607:fc50:1000:9b00::25]) by mx1.freebsd.org (Postfix) with ESMTP id B6EB6FC5 for ; Thu, 21 Feb 2013 18:42:49 +0000 (UTC) Received: from chombo.houseloki.net (montesse-2-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:19b9::2]) by rush.bluerosetech.com (Postfix) with ESMTPSA id E20691141D; Thu, 21 Feb 2013 10:42:48 -0800 (PST) Received: from [127.0.0.1] (ivo.houseloki.net [10.9.70.20]) by chombo.houseloki.net (Postfix) with ESMTPSA id C939F3FD; Thu, 21 Feb 2013 10:42:46 -0800 (PST) Message-ID: <51266AA8.9020605@bluerosetech.com> Date: Thu, 21 Feb 2013 10:42:48 -0800 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: andrew clarke Subject: Re: State of pkgng? References: <51257C50.7000001@bluerosetech.com> <20130221030858.GA45907@ozzmosis.com> In-Reply-To: <20130221030858.GA45907@ozzmosis.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Mailing List 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: Thu, 21 Feb 2013 18:42:49 -0000 On 2013-02-20 19:08, andrew clarke wrote: > On Wed 2013-02-20 17:45:52 UTC-0800, Darren Pilgrim (list_freebsd@bluerosetech.com) wrote: > >> Reading the pkgng page on the wiki: >> >> "As a consequence of the security incident on 11th November 2012, for >> the time being pre-compiled packages for pkgng are not available from >> any official FreeBSD repository. [...] Target dates for when service may >> be resumed have not been released." >> >> Is that still the case? Is pkgng presently a non-starter? > > Just to be clear, pkgng is not broken. You can still use it with the > Ports tree or use it to install locally-built packages. I wasn't clear on that point. Thanks. No, pkgng integrates perfectly with Ports. I have WITH_PKGNG=yes on almost all of my systems. I was following up about the package repo, which is still empty. I do like the speed increase of pkg-version over pkg_version. What can the lowly sysadmin do to speed up getting the pkgng package repo?