Few things

[Codegen]

I finally got portage working properly in Gentoo, soI got KDE running properly and I gotta say it's quite an improvement to the previous versions.

Anyways, here are a few wuestions:

1) Startup Login

Does anybody here know how to change this to something other than the fugly grey boxes?

edit: I'm talking about the ogin screen. It seems to load before it loads KDE - I'm assuming it;'s normal?

2) End new Session

When I go to the menu > Log Out, the only option is to End Session( see image below) How do I add at least the shutdown?

3) Excess Baggage

How do I remove all the crap that I don;t need that Gentoo installed?

I know I'm forgetting something, I'll edit if I do find out.

I'm talking about the KDE packages.

--------EDIT---------

4) How do I cover that boot-up text with a splash screen?

Edited April 4, 2005 by Codegen

[DjmUK]

3) Excess - there is no excess crap, Gentoo is kinda' empty on apps, which is a good thing.

1) Start > Control Centre (I think)

2) I type in the terminal "shutdown -h time 0" <-- or something similar

Not much help, but I tried from my limited experience ;)

[Codegen]

Well, it installs every single KDE package - most of which I have no use for.

Now I remember what the other one was.

[furry_goat]

1) If you're talking about the login manager, KDM, there are various themes you can use to customise it. Alternatively, use another login manager. Entrance is good looking.

2) Gentoo has the shutdown command available for root only. You can bypass this with suid on the appropriate binaries. Refer to this gentoo forum thread for more.

3) Use the KDE split ebuilds.

4) Use vesafb-tng for a framebuffer console and then fbsplash for a nice, high-res animated bootsplash logo.

[Codegen]

But, even when I was in root, the only option wsas to end session.

I'll try the suggestions for everything else, though.

[Codegen]

1) If you're talking about the login manager, KDM, there are various themes you can use to customise it. Alternatively, use another login manager. Entrance is good looking.

2) Gentoo has the shutdown command available for root only. You can bypass this with suid on the appropriate binaries. Refer to this gentoo forum thread for more.

3) Use the KDE split ebuilds.

4) Use vesafb-tng for a framebuffer console and then fbsplash for a nice, high-res animated bootsplash logo.

585724192[/snapback]

1) Oops, just realised that I acciderntily left that line commented in rc.conf

2) ...I'll stick to shutdown-h now

3) I've already put enought ime into this

4) I'll try it.

Thanks.

edit: and nice broken link to your fbsplash ;)

[Codegen]

Look slike I killed 2 birds with one stone on the uncommenting the line. The other shutdown/restart options are there now.

[LaNcom]

To install only parts of KDE, don't use the split ebuilds. They are intended for people not running KDE, but with the desire to use at least some KDE apps (Kate, for example). To reduce the KDE applications, add this to your /etc/make.conf (just an example):

DO_NOT_COMPILE="debian noatun kpackage juk krec kaudiocreator kolourpaint kpovmodeler kppp kget kuickshow artsbuilder kedit kmid kscd kfax kiconedit test examples kruler faxview klaptopdaemon charselectapplet kdelirc kjots lisa cervisia kbabel kbugbuster kcachegrind kmtrace kspy umbrello kstartperf kprofilemethod "

And don't install useless 'krap' like kdetoys, kdeedu or kdegames if you don't need it. That one's simple - instead of using 'emerge kde', use (another example):

emerge arts kdelibs kdebase kdenetwork kdeartwork kdemultimedia kdeadmin kdepim kdeaddons kdeutils kdegraphics

[Codegen]

I'll do the above tommorow. I'll be at school ,so my computer can do all hat crap then.

[furry_goat]

To install only parts of KDE, don't use the split ebuilds. They are intended for people not running KDE, but with the desire to use at least some KDE apps (Kate, for example). To reduce the KDE applications, add this to your /etc/make.conf (just an example):

585726550[/snapback]

There are numerous advantages to running the split ebuilds over the monolithic ones, as outlined on the page linked, even if you wish to install all or most of KDE. Use the meta and then emerge -C && emerge depclean, or use /etc/portage/package.provided to keep unwanted packages out.

DO_NOT_COMPILE="debian noatun kpackage juk krec kaudiocreator kolourpaint kpovmodeler kppp kget kuickshow artsbuilder kedit kmid kscd kfax kiconedit test examples kruler  faxview klaptopdaemon charselectapplet kdelirc kjots lisa cervisia kbabel kbugbuster kcachegrind kmtrace kspy umbrello kstartperf kprofilemethod "

This is the old way of doing things, and certainly not the recommended way now that we have proper split ebuilds. Build-time flags are no substitute for proper package management and dependency handling.

Here is what the Gentoo page says about DO_NOT_COMPILE:

DO_NOT_COMPILE is an environment variable internal to the KDE build system. It allows selectively disabling subdirectories from compilation. Some people used to use it to compile subsets of the monolithic KDE ebuilds. For instance, running DO_NOT_COMPILE=konqueror emerge kdebase would install a kdebase without the konqueror application.

However, DO_NOT_COMPILE was never intended to be used to interfere with the operation of a package manager's automated builds. It does not work, it can break your system, and it was never supported. We request everyone to refrain from using it.

Here is a partial list of the problems with DO_NOT_COMPILE:

• It completely breaks portage's dependency tracking. Portage does not know about DO_NOT_COMPILE, and thinks the entire monolithic package has been installed and can satisfy other packages' deps. This can cause other packages not to emerge or not to run.
  
• It forces the user to know the names and meanings of all the different existing subdirs of the KDE modules. Very few users do know this, unless they're KDE developers, so they can't use DO_NOT_COMPILE properly.
  
• KDE module subdirs can have interdependencies between them, require a particular build order, require another dir to be present even if it does not have to be installed, and so forth. We put a lot of work into the split ebuilds to make them work properly in this regard. DO_NOT_COMPILE is not nearly a fine enough tool to achieve the same results, even given sufficient knowledge on the user's part. The only thing you can do with it is disable a few applications from compiling. It is practically impossible to use it to install only a few selected applications from modules like kdebase or kdepim.
  
• If I installed kmail yesterday and want to add korn today, using DO_NOT_COMPILE, it entails recompiling kmail as well. This means DO_NOT_COMPILE is always much slower than split ebuilds.
  
• DO_NOT_COMPILE can't be used to make precompiled packages (such as the GRP) containing individual KDE apps.
  

[LaNcom]

furry_goat,

while you are right, the split ebuilds are a) cumbersome to use compared to DO_NOT_COMPILE right now, and b) not really that relevant for the dependency handling if you know what packages to keep out. Nothing in the whole wide world depends on kedit or kpovmodeler anyway... :-)

So I'll guess I'll stick to DO_NOT_COMPILE for now, 'till gentoo comes up with an easier, more intuitive way to handle the split ebuilds that is (Like simply using DO_NOT_COMPILE if provided in make.conf to select the split ebuilds accordingly - they could also rename it to KDE_DO_NOT_COMPILE or something while keeping the format, so it wont affect KDE's build system. That would be convenient and made the transition really easy)...