From owner-freebsd-pkgbase@freebsd.org  Fri Jan 29 00:15:29 2016
Return-Path: <owner-freebsd-pkgbase@freebsd.org>
Delivered-To: freebsd-pkgbase@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 5FC3BA70BE0
 for <freebsd-pkgbase@mailman.ysv.freebsd.org>;
 Fri, 29 Jan 2016 00:15:29 +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 21DB0E35
 for <freebsd-pkgbase@freebsd.org>; Fri, 29 Jan 2016 00:15:29 +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 1aOwij-000O0U-IF; Fri, 29 Jan 2016 03:15:25 +0300
Date: Fri, 29 Jan 2016 03:15:25 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Garrett Wollman <wollman@csail.mit.edu>
Cc: freebsd-pkgbase@freebsd.org
Subject: Re: Packaging the FreeBSD base system with pkg(8)
Message-ID: <20160129001525.GH88527@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>
 <22186.43196.374050.48765@khavrinen.csail.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <22186.43196.374050.48765@khavrinen.csail.mit.edu>
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-pkgbase@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Packaging the FreeBSD base system." <freebsd-pkgbase.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-pkgbase>, 
 <mailto:freebsd-pkgbase-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-pkgbase/>
List-Post: <mailto:freebsd-pkgbase@freebsd.org>
List-Help: <mailto:freebsd-pkgbase-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-pkgbase>, 
 <mailto:freebsd-pkgbase-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2016 00:15:29 -0000

On Thu, Jan 28, 2016 at 06:48:12PM -0500, Garrett Wollman wrote:

> <<On Thu, 28 Jan 2016 19:06:22 +0300, Slawa Olhovchenkov <slw@zxy.spb.ru> said:
> 
> > 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.
> 
> We've never supported this for source upgrades; I don't see any reason
> to expect it to work for binary upgrades either.  At a minimum you
> should expect to have to upgrade 11.0 -> latest 11.x -> latest 12.x ->
> ... -> latest 17.x -> 18.0.

You miss some points. Source upgrades suported over-release upgrade
(currently 10-STABLE can be upgraded from 7.0, see Makefile.inc1).
Source upgrade is self-contained and don't depend from environment.
Contrary to binary upgrade may depend of environment: presents pkg.txz
on ftp.freebsd.org, freebsd.org ovned by project and etc. As result,
in case of bad design, you can't upgrade from 11.0 nowhere (ex: packages
for 11.x outdated and deleted, pkg.txz from latest suported release
can't be run on 11.0, pkg from 11.0 can't be parsed latest format).

I am not averse to binary upgrade path like
11.0-12.last-14.last-15.last-16.last-18.0. I am disagree case when
impossible to upgrade outdated install (because url is now incorrect,
packages for outdated release removed or lost and etc).