Date: Thu, 5 Jan 2006 01:06:05 -0800 From: Jo Rhett <jrhett@svcolo.com> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: stable@freebsd.org, current <current@freebsd.org> Subject: Re: HEADS UP: Release schedule for 2006 Message-ID: <20060105090605.GD1358@svcolo.com> In-Reply-To: <20051223043820.GG77268@cirb503493.alcatel.com.au> References: <43A266E5.3080103@samsco.org> <20051217215434.GB92180@svcolo.com> <20051217220807.GA28741@freebie.xs4all.nl> <20051222211019.GI39174@svcolo.com> <20051222213041.GA5746@odin.ac.hmc.edu> <20051222220532.GL39174@svcolo.com> <20051223043820.GG77268@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 23, 2005 at 03:38:20PM +1100, Peter Jeremy wrote: > I agree with Brooks. I don't recall ever seeing a message from -core > (or anyone else talking on behalf of the Project) stating that code to > make binary updates possible would not be integrated. For that matter, > I don't recall ever seeing code offered to implement such a feature. As stated before, let me find some threaded archives and I'll find the relevant topics. Perhaps it wasn't -core that vetoed it, but it was harshly fought against for ivory tower reasons, and nobody from -core ever stood up to show interest. > Core OS packages have been discussed but I don't recall the idea ever > being vetoed. Some work have been done in breaking bits of the base OS > out into packages (perl, games and UUCP come to mind) but packaging the > entire system is a major undertaking. In any case, I don't see how > packaging the system would help you. Taking Solaris as an example of > an OS which is broken up into lots of packages, patches don't replace > whole packages, they replace individual files. Obviously the details need to be ironed out. The current freebsd package system is certainly missing a few key features (in my mind) but most everyone agrees on the basics. Packaged cores allow identification of "what you have". Package databases can store "what you have changed". Package databases can store "how to back out the change". This is pretty much the only things that prevent freebsd-update from working perfectly in production environments, to name the most obvious candidate for adapting to this job. -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060105090605.GD1358>