Date: Thu, 28 Jan 2016 09:28:32 -0800 From: NGie Cooper <yaneurabeya@gmail.com> To: Slawa Olhovchenkov <slw@zxy.spb.ru> 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: <A639FA8D-8922-4BA9-8C24-57B48EFACDAA@gmail.com> In-Reply-To: <20160128160622.GB88527@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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 tim= e where seamless upgrades are not possible, and instead you need to hop from= release to release (this is not ideal, but it could happen). 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 c= hange is, deprecation of platforms and the change in upgrade framework, whic= h requires upgrading from blessed releases proven to work with the new frame= work. Thanks, -NGie=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A639FA8D-8922-4BA9-8C24-57B48EFACDAA>