From owner-freebsd-current@freebsd.org Thu Jan 28 17:03:52 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 AA212A71EFA for ; Thu, 28 Jan 2016 17:03:52 +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 6DC921E91 for ; Thu, 28 Jan 2016 17:03:52 +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 9A262D97F; Thu, 28 Jan 2016 17:03:51 +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> Cc: freebsd-current@freebsd.org From: Allan Jude Message-ID: <56AA4A00.6000103@freebsd.org> Date: Thu, 28 Jan 2016 12:04:00 -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: <20160128170037.GR37895@zxy.spb.ru> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHnBF6QvLjTnx5PltQxCwJceuW11QM6l7" 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:03:52 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xHnBF6QvLjTnx5PltQxCwJceuW11QM6l7 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016-01-28 12:00, Slawa Olhovchenkov wrote: > On Thu, Jan 28, 2016 at 11:09:56AM -0500, Allan Jude wrote: >=20 >>>> Yes, but but real usage of it would happen in a second step because = of many >>>> rought edges to be deal with. but yes the information would be avail= able >>>> >>>> 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 ch= ange 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 available= , >>> 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@freebsd= =2Eorg" >>> >> >> According to our current release schedule, FreeBSD 18.0 will not come >> out for 35 years (2051). >=20 > 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? >=20 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. It is not a burden that RE@ should have to deal with. >> The general approach would appear to be just downloading new packages >> and updating the system. For a drastic upgrade like that, you'd likely= >> have to build a newer version of pkg from ports. >=20 > You kidding. Ports from 18.0 cant't be build on 11.0. This trivial > expirence, ports tree incomatible change every 5-6 years. >=20 >> The approach for offering an upgrade from 10.x to 11.0 will be the mor= e >> interesting endeavour. >=20 > I am guess this is already study. > My interests in long run. >=20 --=20 Allan Jude --xHnBF6QvLjTnx5PltQxCwJceuW11QM6l7 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) iQIcBAEBAgAGBQJWqkoDAAoJEBmVNT4SmAt+MigP/jyhLXn5kn4YSUDoP9ifCo7i X6Ic3BCfipNIGSqG3qBD7RGhahQ3JSzQ93fYK8J7itGX07gznyoUJ3gnY+MtxmtK keu506Kr2Hg9TRxj6HMiGQ+QPuBiuoEOKvTcxo5eZfcZcj/G0EMSc3HW/OzTNumD Ih4sl9XRwP8m+Y8zSFhxGb5SEDUxu6lH4+rusQ+CK7ZNq/x7PamgFWr+uaLT/qix 2PRYCU86PPyt39ETbnjOZQZYJOMxyJ9QwvocELM1/ZlY/0RmRr9iExA9S3i+ZSKK aIieYDea9bV3MTbb011M+DjQwKCBtLo++QyClGSv8egYpX7zPGe7T0ro+2GDSrkl WMFfmz1R5455JztPwAiPlFamNYMdmLNDvHQHdV3NOPwDqVFeZ+9uzIC3Xkp3RSOG GyC4och8A/ZcryGVE/R5+Q+YvYbZT3tIMrqBJ+VqI65etPZDbVUHvQ20yzAW3J6n L+3PYN+Zf1zJiOcZSXRos1qOByXsDkj/nVCAHFdmSjuTAKkuKOqF24qnT5ZRQ9qQ sXn+d8ahRIK2mIeywIVuX7vCH+zeLWDspSs+Buh39zxE/ou5W5fAkviKmFiOyS04 RqW1XJIe/uuaYvpmgGbenO0zZuyRxRJBYiQOY3rwJxcS7VvoThClGPbaMJCVy88K +bm/etUpRKMlP824buRk =TOPt -----END PGP SIGNATURE----- --xHnBF6QvLjTnx5PltQxCwJceuW11QM6l7--