Date: Thu, 28 Jan 2016 09:45:16 -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: <3A5AAF2B-F9CF-41B3-A97C-FF208803428A@gmail.com> In-Reply-To: <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> <20160128173836.GD88527@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Jan 28, 2016, at 09:38, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote: >=20 >> On Thu, Jan 28, 2016 at 09:28:32AM -0800, NGie Cooper wrote: >>=20 >>=20 >>> On Jan 28, 2016, at 08:06, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote: >>=20 >>=20 >> ... >>=20 >>> 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. >>=20 >> 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). >=20 > 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. >=20 >> 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. >=20 > This is common practic, yes. > This is acceptably if possible got all necessary in time 18.0 for > upgrade from 11.0. Yes. Given the hiccups going from pkg 1.4 to 1.6 with the plist stuff, this i= s going to be more entertaining across interface breaks; it might be that pk= gng is at the point where it's stable enough that interfaces won't change (u= nlikely, software tends to be fluid), or backwards compatibility will need t= o be maintained for older versions of pkgng. Also, consider that you're going to be allowing upgrades from older RELEASE v= ersions of the OS which might be using a fixed copy of pkgng -- how are you g= oing to support that? Thanks! -NGIE=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A5AAF2B-F9CF-41B3-A97C-FF208803428A>