Regarding the GRP..... Taken from the handbook..... The Gentoo Reference Platform, from now on abbreviated to GRP, is a snapshot of prebuilt packages users (that means you!) can install during the installation of Gentoo to speed up the installation process. The GRP consists out of all packages required to have a fully functional Gentoo installation. They are not only sufficient to have a base installation up to speed in no time, but all lengthier builds (such as KDE, XFree, GNOME, OpenOffice, Mozilla, ...) are available as GRP packages too. However, these prebuilt packages aren't maintained during the lifetime of the Gentoo distribution. They are snapshots released at every Gentoo release and make it possible to have a functional environment in a short amount of time. You can then upgrade your system in the background while working in your Gentoo environment. Does this mean that after a GRP installation, "emerge -u world" will do future upgrades in the normal (compile from source) manner for those packages?
Or do they have to somehow change from GRP packages to source ebuilds? Regards, Robert Some days you are the pigeon, some days you are the statue. -----Original Message----- From: Nick Rout [mailto:[EMAIL PROTECTED] Sent: Tuesday, 6 April 2004 12:09 p.m. To: [EMAIL PROTECTED] Subject: Re: Gentoo Installfest On Tue, 06 Apr 2004 11:07:14 +1200 "Fisher, Robert (FXNZ CHC)" <[EMAIL PROTECTED]> wrote: > We could use my box as a demo machine I suppose. I could put off doing > etc-update on my box until the day so we can show this. > > I wonder if you have suggested too many topics Nick? There could be a risk > of taking on too much in one session. possibly, its not exactly KISS is it. dispatch-conf is an alternative to etc-update. ufed edits your USE flags in a nice little curses gui. distcc is, i agree, superfluous and there is a good howto on the gentoo site. what order would you do these things in? overview (so the remaining stuff makes sense) /etc/make.conf important variables SYNC= etc emerge rsync emerge & USE flags together, discussion of "world" initscripts (which I forgot earlier) actually come to think of it the materials for this are there in the second part of the handbook http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=0 (actually don't bother looking there now, they are having problems) we just need to be able to run through it briefly and make sure everyone has a grip on the basics. > > I have got by so far without knowing anything about etcat, qpkg or > dispatch-conf. I do not use ufed and most home users may not use distcc. > > Other subjects are essential though IMHO. > > Regards, Robert > Some days you are the pigeon, some days you are the statue. > > -----Original Message----- > From: Nick Rout [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 6 April 2004 9:51 a.m. > To: [EMAIL PROTECTED] > Subject: Re: Gentoo Installfest > > OK people who are attending the gentoo mini installfest, you can see > what Brad's suggestion is - include a little talk on maintaining your > gentoo distro. Who is going to do this and prepare a set of materials? I > will do some of it, and present if necessary, but help will be needed. > > My suggestion is to use the same xml schema as the gentoo documentation > on their site, and possibly submit it to them afterwards, if its deemed > good enough. > > Helpers/contributors? > > Random thoughts on topics:- > > emerge > etcat > qpkg > USE flags > ufed > distcc > SYNC= > GENTOO_MIRRORS= > etc-update > dispatch-conf > blocked builds > > > > On Fri, 26 Mar 2004 12:58:56 +1200 > Brad Beveridge <[EMAIL PROTECTED]> wrote: > > > As to the GenInstall, my thoughts would be that punters would be best > > getting a GRP install done, with KDE, X, etc going. Then a session on > > using emerge to maintain your distro. The settings are the hard part to > > get right & that is what time should be spent on, not waiting for > > compiles. Not matter how big a compile farm you have, compiling still > > takes a long, long time - and it can be done off line later without the > > support of others. > > > > Brad > > -- > Nick Rout <[EMAIL PROTECTED]> -- Nick Rout <[EMAIL PROTECTED]>
