From owner-freebsd-current@freebsd.org Thu Jan 28 17:44:57 2016 Return-Path: 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 83634A712C3 for ; Thu, 28 Jan 2016 17:44:57 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 4608A1C34 for ; Thu, 28 Jan 2016 17:44:57 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 6B92BDA73; Thu, 28 Jan 2016 17:44:56 +0000 (UTC) Subject: Re: Packaging the FreeBSD base system with pkg(8) To: Slawa Olhovchenkov References: <20160127223323.GG98557@FreeBSD.org> <183431.62409.bm@smtp111.sbc.mail.ne1.yahoo.com> <20160128131806.GB67200@ivaldir.etoilebsd.net> <20160128160622.GB88527@zxy.spb.ru> <56AA3D54.5020502@freebsd.org> <20160128170037.GR37895@zxy.spb.ru> <56AA4A00.6000103@freebsd.org> <20160128172555.GC88527@zxy.spb.ru> Cc: freebsd-current@freebsd.org From: Allan Jude X-Enigmail-Draft-Status: N1110 Message-ID: <56AA53A1.2080807@freebsd.org> Date: Thu, 28 Jan 2016 12:45:05 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <20160128172555.GC88527@zxy.spb.ru> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mDAIiRpmJPcicCQMUmbxJDHDe4cjiRigB" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Thu, 28 Jan 2016 17:44:57 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --mDAIiRpmJPcicCQMUmbxJDHDe4cjiRigB Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016-01-28 12:25, Slawa Olhovchenkov wrote: > On Thu, Jan 28, 2016 at 12:04:00PM -0500, Allan Jude wrote: >=20 >> On 2016-01-28 12:00, Slawa Olhovchenkov wrote: >>> On Thu, Jan 28, 2016 at 11:09:56AM -0500, Allan Jude wrote: >>> >>>>>> Yes, but but real usage of it would happen in a second step becaus= e of many >>>>>> rought edges to be deal with. but yes the information would be ava= ilable >>>>>> >>>>>> see: >>>>>> https://www.youtube.com/watch?v=3DBr6izhH5P1I >>>>>> and >>>>>> https://www.youtube.com/watch?v=3Dv7px6ktoDAI >>>>>> >>>>>> for a bigger view of what happened (note that some detail my have = change a bit, >>>>>> the overall remains the same) >>>>> >>>>> What about upgrade strongly outdated system? >>>>> For example 11.0 at time 18.0? I.e. packages for 11.0 don't availab= le, >>>>> pkg from 11.0 don't undertund package base from 18.0 and etc. >>>>> _______________________________________________ >>>>> freebsd-current@freebsd.org mailing list >>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freeb= sd.org" >>>>> >>>> >>>> According to our current release schedule, FreeBSD 18.0 will not com= e >>>> out for 35 years (2051). >>> >>> Schedule may be changed. >>> How you calculate this? As I see next mayor release gone in 2 year. >>> 18-11=3D7, 14 years, in 2030. >>> Ok, let 15.0 or 16. >>> I am work from FreeBSD 2.0, I am use (now) installation with 5.4, why= >>> I can't planed about 11 to 18 upgrade? >>> >> >> You are correct sorry, I was thinking of the 5 year lifecycle of each >> release, not the 2 year cadence of new releases. >> >> Upgrading from an End-of-Life release is specifically not supported. >=20 > Where is documented? Curently source based upgraded suported to last > stable direct from 7.0. Last supported release now is 9.3. > Upgrade to 7.0 supported from 5.3. > Upgrade to 5.3 supported from, hmm, I think last 3-STABLE (or any 3.x?)= =2E > Upgrade from 2.x to 3.x is aout-elf upgrade. > As result, source upgrade supported in 3 step upgrade from any current > elf release to last stable. > Because ALL source history preserved. > I think preserving all binary packages from previos releases is imposib= le. >=20 >> It is not a burden that RE@ should have to deal with. >=20 > Please distinguish 'not supported' and 'prohibited'. > This position reduce to 'lost time to system upgrade? format C: and ins= tall > any other OS with more liberal upgrade policy'. > Time to system upgrade may be lost by multiple reasons, for example -- > lost previos staff. >=20 I definitely meant 'not supported', and did not mean to imply prohibited. I believe RE@ is only required to maintain an upgrade path from older supported releases, to the newer supported releases. Everything else is best effort. SRC upgrades from 7.0 are not guaranteed, but we do our best to not break them unnecessarily. --=20 Allan Jude --mDAIiRpmJPcicCQMUmbxJDHDe4cjiRigB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJWqlOkAAoJEBmVNT4SmAt+cdgQALsTAor3J+XlQXLmgCO7ya7n 1Tr6vp9m8GOHNhfx86mjDREcE3ONebk2hpjggOpwQbmJ5lFPvXCtcFK6p80aiTC+ tuoeXYYc1LebVubBfuSeCaSi6ug40xZ7cFpPVnzF9jdeDc9UteFog7id86slWGzH Wc6FZBKsv6p1I/E8lzvvyOFMGnDtJYXpYHeMLD+m488n+WDN5a6fgrV0XUdj9VzE GOYhWl7y5bMEdTlRLJoTsVrb0guMVbE7Xp6ckVXP7NMxHqoE6Ce8eptpvuHOJTgP ygsSX8/vguPl+h0DjPSKY06oub2UXAg+P9PQQ2mTIUcd0TTPTnobBR0iF8mz3td8 LOaHiOQPNJTqL6Nagg62WJg1ofUlA5mRTeJYP82gwR59j0Q+cHIX1NNq7bArdMSH aif0TCalbyYxVdyp1mck7FCqMo5N8px9O2l24elOvH5Yi5JNxTtBLi9f9WjVxJyJ 0r6U+cSRoAMfrqaSut+c7aDH0JGPrp0VkJl5we9GlDjgbye3D4Mnf2YcLo4HQS81 5Ze6XGmKOQK7dpg1LvCWKLrU1H7DijC0gOsQ9eAGjxRU1DKJTuyIRpcLjRcFULRC 6SwmU83474lmsTNhS4+CqLGby+RqOrwvKNhebrxYrZbRQZOF2AyBB3dkbUiWVbYV gb5Iq0wzQDNlkja5sL7a =rsCF -----END PGP SIGNATURE----- --mDAIiRpmJPcicCQMUmbxJDHDe4cjiRigB--