From owner-freebsd-current@freebsd.org  Thu Jan 28 17:38:40 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FDDDA70F21;
 Thu, 28 Jan 2016 17:38:40 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2F98B1551;
 Thu, 28 Jan 2016 17:38:40 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1aOqWj-000F9Y-1j; Thu, 28 Jan 2016 20:38:37 +0300
Date: Thu, 28 Jan 2016 20:38:37 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: NGie Cooper <yaneurabeya@gmail.com>
Cc: Baptiste Daroussin <bapt@FreeBSD.org>,
 Thomas Mueller <mueller6724@bellsouth.net>,
 freebsd-current@freebsd.org, freebsd-pkgbase@freebsd.org
Subject: Re: Packaging the FreeBSD base system with pkg(8)
Message-ID: <20160128173836.GD88527@zxy.spb.ru>
References: <20160127223323.GG98557@FreeBSD.org>
 <183431.62409.bm@smtp111.sbc.mail.ne1.yahoo.com>
 <20160128131806.GB67200@ivaldir.etoilebsd.net>
 <20160128160622.GB88527@zxy.spb.ru>
 <A639FA8D-8922-4BA9-8C24-57B48EFACDAA@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A639FA8D-8922-4BA9-8C24-57B48EFACDAA@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2016 17:38:40 -0000

On Thu, Jan 28, 2016 at 09:28:32AM -0800, NGie Cooper wrote:

> 
> > On Jan 28, 2016, at 08:06, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote:
> 
> 
> ...
> 
> > What about upgrade strongly outdated system?
> > For example 11.0 at time 18.0? I.e. packages for 11.0 don't available,
> > pkg from 11.0 don't undertund package base from 18.0 and etc.
> 
> This is an important question to ask and solve. There might be
> points in time where seamless upgrades are not possible, and instead
> you need to hop from release to release (this is not ideal, but it
> could happen).

I see two side of this problem: support in sofware and support in
infrastructure (ftp.freebsd.org and etc.). Because pkg is not part of
base FreeBSD and live in ports -- this hops need to preserve (and
testing?) packages collections for all past releases and don't move it
to archive. And regular resigning package databases. And I miss
somewere.

> For instance, at $work we're allowing upgrades from version X to Y,
> and Y to Z, but not direct upgrades from X to Z. Part of the
> rationale behind this change is, deprecation of platforms and the
> change in upgrade framework, which requires upgrading from blessed
> releases proven to work with the new framework.

This is common practic, yes.
This is acceptably if possible got all necessary in time 18.0 for
upgrade from 11.0.