From owner-freebsd-current@freebsd.org Thu Jan 28 17:00:39 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 D2A1EA71CC0 for ; Thu, 28 Jan 2016 17:00:39 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 941D41ADE; Thu, 28 Jan 2016 17:00:39 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1aOpvx-000EBA-A1; Thu, 28 Jan 2016 20:00:37 +0300 Date: Thu, 28 Jan 2016 20:00:37 +0300 From: Slawa Olhovchenkov To: Allan Jude Cc: freebsd-current@freebsd.org Subject: Re: Packaging the FreeBSD base system with pkg(8) Message-ID: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56AA3D54.5020502@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false 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:00:39 -0000 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? > 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.