Marcus Priesch wrote: > > > i also thought about building bin-pkgs and distributing them on the > > > targets ... > > > > I'd like this too. In practice, catalyst uses tbz2s behind the > > scenes, so everything doesn't have to be rebuilt every time. > > yes, but what about after a emerge --sync ?!?!
You write explicit snapshot you want to work with in each spec file. > - the problem with working with "outdated" portage trees is - > despite that you dont have all the bugs fixed - that the .tgz's > become unavailable after some time .... thats why i want to stay > "tuned" ... If you need to keep old versions I would recommend mirroring them locally. If you are really serious you'll create your own snapshots too. > furthermore updating a 2 year old gentoo system could be very time > consuming .... thats also a reason why i want to stay up to date ... This is a design decision. If you want to update your systems often then go ahead. But catalyst will require you to at least create a new spec file each time. > and i doubt that catalyst really supports this in a better way than > plain portage does ... at least the reusability of the components > is no plus than either ... What is "better" in your opinion. The massive advantage with catalyst is that one or a few trivial files reliably generate the same system image over and over. The spec files also serve as documentation, or source code for your system if you like. If you don't appreciate this then there's no point in using catalyst at all, but I do think catalyst can work for you. > > Right, this is a good question, catalyst just makes tbz2s of the > > normal packages and applies cleanup stuff at the end, so the tbz2s > > themselves are not very deployable. > > yup ... what about "config-protect" - can this be "mis"used for > such a function ?!?! No, not to control individual files I think, only on the directory level. I believe there is a newish feature in emerge/portage that allows you to specify which files should actually go into root from image/ but last I heard I think there was some bug with it. //Peter
