On Wed, 2005-01-05 at 14:01 -0500, Mike Frysinger wrote: > On Wednesday 05 January 2005 01:36 pm, Marius Mauch wrote: > > Honestly I don't know if stage1 ever had a fully populated /var/db/pkg, > > could be that it was always done that way and just nobody noticed. > > i'm pretty sure it has been > > the way release media (i.e. stages) is created was always a dark art no one > knew anything about (except a few core people). then catalyst came along and > it inherited a lot of the dark baggage (and none of those core people)
I definitely see a lot of it every time I delve into the catalyst code. Piece by piece the old stuff is being replaced with things that make more sense. > theres no point in getting angry at people over 'lack of bugs' and such ... > people just dont know how things 'should be done' because this is just the > way it's *always* been done (at least as long as they've been here) ... that > probably includes zhen :). i myself have asked questions about why certain > things are done in a stage1 and no one replies (-> no one knows, the people > who do are long gone) I can understand that. > i'll happily work with you in getting bootstrap.sh up-to-speed with stage1's > that include a full /var/db/pkg ... i dont think many here have been around > long enough to know how much work (read: hacks) it took in the past just so > that people going from a stage1 didnt have to build their toolchain > (gcc/glibc) twice. nor should a toolchain be built twice imho. Sweet. This is really the only part holding me back. I can commit the fixes to catalyst to not clean /var/db/pkg right now, if you want. That will give you something to work against. -- Chris Gianelloni Release Engineering - Operational/QA Manager Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
