Date: Fri, 29 Jan 2016 04:05:24 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Garrett Wollman <wollman@csail.mit.edu> Cc: freebsd-pkgbase@freebsd.org Subject: Re: Packaging the FreeBSD base system with pkg(8) Message-ID: <20160129010524.GI88527@zxy.spb.ru> In-Reply-To: <22186.45987.44063.515924@khavrinen.csail.mit.edu> References: <20160127223323.GG98557@FreeBSD.org> <183431.62409.bm@smtp111.sbc.mail.ne1.yahoo.com> <20160128131806.GB67200@ivaldir.etoilebsd.net> <20160128160622.GB88527@zxy.spb.ru> <22186.43196.374050.48765@khavrinen.csail.mit.edu> <20160129001525.GH88527@zxy.spb.ru> <22186.45987.44063.515924@khavrinen.csail.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 28, 2016 at 07:34:43PM -0500, Garrett Wollman wrote: > > Source upgrade is self-contained and don't depend from environment. > > Contrary to binary upgrade may depend of environment: presents pkg.txz > > on ftp.freebsd.org, freebsd.org ovned by project and etc. As result, > > in case of bad design, you can't upgrade from 11.0 nowhere (ex: packages > > for 11.x outdated and deleted, pkg.txz from latest suported release > > can't be run on 11.0, pkg from 11.0 can't be parsed latest format). > > You can always build your own release-package repository, stepping Another question is about complexity own release repository. For example, own freebsd-update server is too complex and incorrectly build. > through the intermediate source releases just as you would do now. > All you need to do is preserve the last release package set you build > from each stable branch. I am talk about SUDDENLY discovered outdated setup.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160129010524.GI88527>