Date: Wed, 1 May 2019 14:31:57 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: kris@ixsystems.com Cc: 'Garrett Wollman' <wollman@csail.mit.edu>, 'Cy Schubert' <Cy.Schubert@cschubert.com>, freebsd-pkgbase@freebsd.org Subject: Re: CFT: FreeBSD Package Base Message-ID: <20190501113157.GI2161@zxy.spb.ru> In-Reply-To: <081a01d4ff84$fa4f3d50$eeedb7f0$@ixsystems.com> References: <freebsd-rwg@gndrsh.dnsmgr.net> <201904291441.x3TEfMid072751@gndrsh.dnsmgr.net> <201904291931.x3TJV73d079802@slippy.cwsent.com> <23751.25464.908633.101215@khavrinen.csail.mit.edu> <8B10CAFD-88A1-4DAD-92C2-93F5DE4B3402@cschubert.com> <23752.34284.56207.860696@khavrinen.csail.mit.edu> <081a01d4ff84$fa4f3d50$eeedb7f0$@ixsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 30, 2019 at 02:46:09PM -0400, kris@ixsystems.com wrote: > > > -----Original Message----- > > From: owner-freebsd-pkgbase@freebsd.org <owner-freebsd- > > pkgbase@freebsd.org> On Behalf Of Garrett Wollman > > Sent: Tuesday, April 30, 2019 1:29 PM > > To: Cy Schubert <Cy.Schubert@cschubert.com> > > Cc: freebsd-pkgbase@freebsd.org > > Subject: Re: CFT: FreeBSD Package Base > > > > > Which begs the question, if we're simply replacing freebsd-update and > > > it does most of what we want why the extra effort? > > > > Anyone who isn't using a completely stock make.conf/src.conf is already > > replacing freebsd-update, and it would be much *less* effort to have only > > one mechanism to distribute software rather than two. > > > > I'd like to have a better installation process, too, because that would make it > > much easier to redeploy servers. But most of our servers are file servers > > with unique user data so "redeploy" is not a relevant operation much of the > > time. > > > > -GAWollman > > > > _______________________________________________ > > freebsd-pkgbase@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-pkgbase > > To unsubscribe, send any mail to "freebsd-pkgbase- > > unsubscribe@freebsd.org" > > > This was a big motivator for us to merge base pkgs into poudriere. > In my career I've written 4 build systems that all do some variation > of buildworld/kernel + poudriere + create ISO + create updates. I'm > sure plenty of other FreeBSD consumers have done the same, and > frankly its getting old. At least now I'm down to poudriere + create > ISO only. svnlite export foreach patch patch -E -p0 -z '' sh release.sh release.conf tar -xf $R/R/ftp/base.txz --strip-components 5 -C tmp ./var/db/etcupdate/current/ tar -cf $R/R/ftp/etcupdate.tar -C tmp . and update find -x . -flags +schg | xargs chflags noschg fetch -qo - http://pkg/update12/doc.txz | tar xf - fetch -qo - http://pkg/update12/kernel.txz | tar xf - fetch -qo - http://pkg/update12/kernel-dbg.txz | tar xf - fetch -qo - http://pkg/update12/lib32.txz | tar xf - fetch -qo - http://pkg/update12/base.txz | tar xf - --exclude ./boot/device.hints ./COPYRIGHT boot dev media mnt proc tmp bin lib libexec rescue sbin usr var/yp/Makefile.dist > > And my sympathies to anybody still having to use freebsd-update as part of their custom updating process 😉 freebsd-update take x4 time and space to build, constantly broken, slow update on client and take too much space and files on client. And have fixed bindings for run on official freebsd-update cluster. I am don't use it anymore.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190501113157.GI2161>