huh... seems to be caused by the option 'download all packages before installing...' ----- Original Message ---- From: Josh Coffman To: Main PLUG discussion list Sent: Thursday, October 19, 2006 12:14:45 PM Subject: Re: sabayon I'm not doing something right... I installed suprtux with kuruu, but when I try to install gimp, mplayer-plugin, or others it acts like its installing but gives me an emerge message popup. looks like this: libgnomecups-0.2.2.tar.bz2 MD5 ;-) ... [ ok ]
libgnomecups-0.2.2.tar.bz2 RMD160 ;-) ... [ ok ]
libgnomecups-0.2.2.tar.bz2 SHA1 ;-) ... [ ok ]
libgnomecups-0.2.2.tar.bz2 SHA256 ;-) ... [ ok ]
libgnomecups-0.2.2.tar.bz2 size ;-) ... [ ok ]
checking ebuild checksums ;-) ... [ ok ]
checking auxfile checksums ;-) ... [ ok ]
checking miscfile checksums ;-) ... [ ok ]
checking libgnomecups-0.2.2.tar.bz2 ;-) ... [ ok ]
libgnomeprint-2.12.1.tar.bz2 MD5 ;-) ... [ ok ]
libgnomeprint-2.12.1.tar.bz2 RMD160 ;-) ... [ ok ]
libgnomeprint-2.12.1.tar.bz2 SHA1 ;-) [snipped] -j ----- Original Message ---- From: Patrick C To: Main PLUG discussion list Sent: Wednesday, October 18, 2006 11:06:45 PM Subject: Re: sabayon Did you read the Sabayon Linux forum post I linked to? In it, I provided examples of how to check for installed software, prepare to install software (decide what options you want), and install it, using real examples. That post also has links to the official Gentoo documentation on it, which is pretty good stuff, too. If Kuroo is complaining when you start it up, do an "emerge --sync && emerge portage" as root to update your portage tree (list of available programs) and portage itself. Portage is essentially a gigantic repository of sources (as well as some binaries). When you run "emerge ", portage downloads the source from a Gentoo mirror, then checks what options you told it to compile with (you can change these using USE flags), and compiles and installs it. It also has standard places of putting things, so if you merge two packages that need each other, they will know where to find each other. It automatically handles dependencies. Portage uses one file directly in /etc (/etc/make.conf) and several files in /etc/portage to determine settings. make.conf: Tells portage what to compile for, your optimizations, your global USE flags, your languages, and your overlays (a portage overlay is like a third-party extension to the portage tree). In /etc/portage we have: package.mask: portage will treat packages in this file as if they don't exist. This can be nice if you want to avoid upgrading to a buggy version of a package. For example Amarok 1.4.2+ was giving me trouble, so up until 1.4.3-r1 came out, I had ">=media-sound/amarok-1.4.2" in my /etc/portage/package.mask file. package.unmask: same idea, but for unmasking packages. I have a few packages listed in mine, including "www-client/mozilla-firefox" and "net-im/gaim" in here. package.use: a list of package specific USE flags. Those are the only ones you really need to mess with. Hope that helps! --Patrick C. --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change you mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change you mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss