Date: Thu, 28 Jan 2016 12:04:00 -0500 From: Allan Jude <allanjude@freebsd.org> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: freebsd-current@freebsd.org Subject: Re: Packaging the FreeBSD base system with pkg(8) Message-ID: <56AA4A00.6000103@freebsd.org> In-Reply-To: <20160128170037.GR37895@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> <56AA3D54.5020502@freebsd.org> <20160128170037.GR37895@zxy.spb.ru>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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 because of many >>>> rought edges to be deal with. but yes the information would be available >>>> >>>> see: >>>> https://www.youtube.com/watch?v=Br6izhH5P1I >>>> and >>>> https://www.youtube.com/watch?v=v7px6ktoDAI >>>> >>>> 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 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.org" >>> >> >> According to our current release schedule, FreeBSD 18.0 will not come >> 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=7, 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. 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. > > You kidding. Ports from 18.0 cant't be build on 11.0. This trivial > expirence, ports tree incomatible change every 5-6 years. > >> The approach for offering an upgrade from 10.x to 11.0 will be the more >> interesting endeavour. > > I am guess this is already study. > My interests in long run. > -- Allan Jude [-- Attachment #2 --] -----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-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56AA4A00.6000103>