On Monday 14 August 2006 16:52, James wrote: > Some time ago, I upgraded several systems I manage. > First was the (painful) upgrade of kde-monolith > to kde-meta. [1] > > Then the easier of the two xorg 6.8 to xorg 7.0. [2] > > I have kept these pacakges masked for a while on other systems, > some of which I only get possession of sporadically for critical/huge > upgrade. > > So my questions are: > > 1. Are these still the most updated urls?
I believe so. > 2. Which should be performed first kde monolithic-->meta > or Xorg to Xorg-modular? Definitely the Xorg monolithic to modular upgrade. KDE is based on X.org. Not the other way around... Further X.org was contrary to KDE made modular by upstream. This means that monolithic X.org is no longer supported. Monolithic KDE is still supported and hence you don't really have to make that change. > 3. Is there any method to streamline/automate these tasks > so that the machines compile the new software overnight, unattended? [...] > thoughts and recomendations are most welcome. First you need to decide if you want all of X.org (virtual/x11) or a more minimal install (xorg-base/x11-xorg). Likewise you need to decide if you want all of KDE (kde-base/kde-meta) or only selected apps or something in the middle. Also if these computers aren't too different (i.e. the CFLAGS are alike - same arch) from each other it might be worth the effort to make use flags the same and create a binhost. That way after compiling it on one computer with FEATURES="buildpkg" you wouldn't have to compile them again for any of the remaining computers. Just make the binary packages available via e.g. ftp and set the PORTAGE_BINHOST variable on the computers while you have them. Then you can use emerge --getbinpkg to emerge the packages... -- Bo Andresen
pgpy6DE7SiauW.pgp
Description: PGP signature
