From owner-freebsd-current@FreeBSD.ORG Sat Jul 14 23:28:07 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B65A81065674 for ; Sat, 14 Jul 2012 23:28:07 +0000 (UTC) (envelope-from bsd-src@helfman.org) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id F16068FC0C for ; Sat, 14 Jul 2012 23:28:06 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so1829882wgb.31 for ; Sat, 14 Jul 2012 16:28:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=KAfnFwx9FkMNvQup2B8RlMJin9kXpMNQFFFyXIDl6lo=; b=L0EhxLnswVWcd/F0OsHYVQEh3JvOFDbTFtC11dY5zh0tZ0PpSjQlN+CrznSugeXQCX cYHQtmohxkwY6qxmlGV+34BSYBjY89pWDzgiyf8ltDVwslr0kaF/JK/xVDtJNeVMe/Oz cQHq0XubkXAHit3y+yDHKt0deDad8YxAqsh5YGG/Hyr0R7+klZLFb49s9UoCoHPNDJZ3 j7guSMRqiDbaPL/ocnKaLVCWncqr5YAFoDbnj3ZXQYgbF0+lP/+mGS3QJqLeLoMRqP5Y Dp94mKMowQXmWANH0t/O08mYRJR/08hD5RyJzN+3qEzJHr4J/ywl7g/oeA6uKGsg1fF5 ZceA== MIME-Version: 1.0 Received: by 10.216.36.71 with SMTP id v49mr3109950wea.70.1342308485711; Sat, 14 Jul 2012 16:28:05 -0700 (PDT) Sender: bsd-src@helfman.org Received: by 10.194.45.133 with HTTP; Sat, 14 Jul 2012 16:28:05 -0700 (PDT) In-Reply-To: References: <20120712100110.GA34228@ithaqua.etoilebsd.net> <4FFF1C09.2020408@FreeBSD.org> <20120712220207.GD49382@ithaqua.etoilebsd.net> <4FFF5983.3010708@FreeBSD.org> <4FFFD944.1030005@ranner.eu> <5000113D.2000004@a1poweruser.com> Date: Sat, 14 Jul 2012 16:28:05 -0700 X-Google-Sender-Auth: DvXK1jOJTx0wuKSij22RgwEAt0I Message-ID: From: Jason Helfman To: Peter Wemm X-Gm-Message-State: ALoCoQmj4edPIaK5fud6WebbedoYdh9nAFCQRiDrn/aAo6P04nOK446jH5ip7DWau8TBubYyq9UZ Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: ports@freebsd.org, Fbsd8 , current@freebsd.org Subject: Re: [HEADSUP & CFT] pkg 1.0rc1 and schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jul 2012 23:28:07 -0000 On Fri, Jul 13, 2012 at 1:41 PM, Peter Wemm wrote: > On Fri, Jul 13, 2012 at 5:14 AM, Fbsd8 wrote: > > What I want to know is this new pkg system going to remove the > requirement > > of having the complete ports tree on my system? > > > > What I am looking for in an port system, is to install a port and any > files > > needed for the parent port and its dependents to automatically be > > downloaded. So in the end my system ports tree only contain the files > used > > to install the ports I use and their dependents. > > That is precisely what pkgng is for. > > At the risk of over-simplifying: > * Generally eliminate the need for having /usr/ports installed for end > user consumers of freebsd if you have no desire to compile ports with > custom options. > * Generally eliminate the need for layers over the top of pkg* like > portupgrade/portmaster/portmanager for those people. > * Play nicely with people who *are* building some (or all) of their > packages from /usr/ports. > * Provide enough look and feel compatibility with the old pkg_* tools > so people will feel enough at home. > * Assimilate an existing pkg_* machine. > * Store complete metadata so that going foward we have much better > support for package sets - eg: package repositories with custom > options that play nicely with official packages. > * Be extensible so that we can add to it as we go forward. > > In the new world order, things like portupgrade and portmanager tend > to be used to manage interactions between personally build ports from > /usr/ports and external binary packages. If you continue to build > from /usr/ports, the only thing that changes is bsd.port.mk uses a > different command to register a package and you still use > portupgrade/portmaster/whatever to orchestrate your personal package > rebuilding. (Well, portmaster does if you apply the simple patch to > it). > > pkg-1.0 is primarily an infrastructure change. Instead of metadata > being stored in discrete +FOO and +BAR files in a .tgz file, it is > stored in a structured, extensible file. Instead of an incomplete set > of metadata being stored in /var/db/pkg/* and having to be augmented > by reaching over to /usr/ports/*, a full set of data is stored in a > .sqlite file. Instead of version numbers being baked into the package > name as an ascii string, the package system uses version numbers as > first class metadata. > > In reality, not much will change at the switch throwing, except that > of having good reason to be afraid of "pkg_add -r", you'll be able to > reasonably expect it's replacement (pkg install) to work. And a bunch > of people who have a /usr/ports tree will suddenly wonder why they > even have it there at all. It becomes incredibly convenient and fast > to use packages. > > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; > KI6FJV > "All of this is for nothing if we don't go to the stars" - JMS/B5 > "If Java had true garbage collection, most programs would delete > themselves upon execution." -- Robert Sewell > > I am by no means speaking for the pkgng direction, goal or for portmgr, but I thought that this thread message spoke to the goal pretty clearly for me. http://lists.freebsd.org/pipermail/freebsd-ports/2012-June/076395.html If this is in fact the case, I don't know if this is documented anywhere. -jgh -- Jason Helfman | FreeBSD Committer jgh@FreeBSD.org | http://people.freebsd.org/~jgh