From owner-freebsd-current@FreeBSD.ORG Sat Sep 1 19:59:16 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5C75F106564A; Sat, 1 Sep 2012 19:59:16 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 065138FC14; Sat, 1 Sep 2012 19:59:15 +0000 (UTC) Received: by obbun3 with SMTP id un3so9665354obb.13 for ; Sat, 01 Sep 2012 12:59:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TR7UUSO1UAGNc+uo6CRuT4l/meK0P9hd6AZeX5Qqwvg=; b=BXDQUFHLx6iwVyW9hd0xnvLd3XhE28vuC0EdcB5HPLzsMP9N4GMQkwhH53yzdhUvSo XrrEff4v1Box+a/nqxXYqPm9eR1edIiyUWlWodCuMQN5oErClzSZDCiDradP8iIZ1Zm0 IlxW1Ab4uaJQBMotHqUtECw3IXevVYHXR4w14TmdRCv7KGbGT3/f9JlxiLFvt+AERVwu Y9jd4GNmDEgB5fPUffkoq7ZICaEfPRLeEu+IaT1yMtbsYwItRF7eBvcB2zAhvSzdKXnB Ok6AWR5lDoRyfYwpUbEe6ntBtP8FjCakgjTi2RDbmIAfyaacnx9gJ6A+w+EK3TidC1Pc 3VOw== MIME-Version: 1.0 Received: by 10.182.31.102 with SMTP id z6mr10927434obh.66.1346529554905; Sat, 01 Sep 2012 12:59:14 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Sat, 1 Sep 2012 12:59:14 -0700 (PDT) In-Reply-To: <50426493.7050302@FreeBSD.org> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <503FF0EE.2020605@FreeBSD.org> <20120831095910.GQ64447@ithaqua.etoilebsd.net> <201208310810.50725.jhb@freebsd.org> <20120831122211.GS64447@ithaqua.etoilebsd.net> <50424956.4090804@freebsd.org> <50426493.7050302@FreeBSD.org> Date: Sat, 1 Sep 2012 12:59:14 -0700 Message-ID: From: Garrett Cooper To: Matthew Seaman Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap 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, 01 Sep 2012 19:59:16 -0000 On Sat, Sep 1, 2012 at 12:40 PM, Matthew Seaman wrote: > On 01/09/2012 18:43, Tijl Coosemans wrote: >> In this scenario the ports tree needs to keep support for older releases, >> but that's a consequence of the fact that there's only one ports tree for >> all releases. Somewhere in between the ports and the various releases there >> has to be some form encapsulation, not just for pkg, but for all the tools >> used by the ports tree. Given how the ports tree currently encapsulates >> both the old and new pkg tools I don't see how supporting multiple versions >> of pkgng would be a problem because presumably the difference between pkgng >> versions is going to be much smaller than the difference between the old >> and new tools. > > New functionality already in the process of development will entail > making non-backwards compatible changes to the DB schema. If we're tied > to supporting a version of pkgng bundled with a release, that's going to > make rolling out such changes much harder. On the other hand, if pkgng > is in ports, then we can release a new version and simultaneously > publish new package sets (incorporating the update to pkgng) from the > repositories which will have been built using the updated DB schema. > > The ports tree doesn't track the versioning of the base system, and it > makes perfect sense to me that tools for dealing with the ports should > follow changes to ports rather than changes to the base. Again, this is part of the reason why I suggested multiple release trains. Although it's more painful for bapt@, et all, it's ultimately what would need to be done in order for pkgng to be packaged with a release or set of releases. I would be happy to assist with this -- it's the least I could do. Thanks, -Garrett