Andrea Olivato’s Blog

Here’s how to get a personalized and satisfactory completion on Gentoo installations..

Fisrt of all you need an use flag set widely in your system so that every software you are going to emerge (or re-emerge) if is capable will be added to your completition choices. To do so just open our magic make.conf with your favourite editor (I use vim, you can use emacs, nano, pico…i don’t really care about wars)
# vim /etc/make.conf
then find the USE variable and add inside it the string
bash-completion
Now you have the option to re-emerge all previously installed programs that have bash-completition USE flag. To do so just do
# emerge -a --newuse world
Right now you got the correct completitions available but to use them you need to install the bash completition ebuild so…
# emerge -avtD app-shells/bash-completion app-shells/gentoo-bashcomp
After emerging the ELOG will tell you to add a string to your .bashrc to enable it. So for each user you want to enable bash completition just edit their own .bashrc.
$ vim ~/.bashrc
Obviously you can do it for root account too (for emerge f.e.)
# vim /root/.bashrc
Right now you got it configured but no program is really affecting your bash shell. To do so I suggest you to use eselect (if you don’t have it just emerge it).

Fist of all use eselect to list all your available programs
# eselect bashcomp list
Then just choose wisely the programs you would like to add and insert them using their ID (the number beetween squares [] ).
# eselect bashcomp enable 1

Done! I usually like adding just a few completition like the emerge one (called gentoo, it adds other completitions then emerge alone) , subversion and git…

I submitted asdGB to the two most used gnome apps websites. You can find my work on the following links

Gtk Apps

Gnome Files

I noticed that even upgrading to latest version of autounmask (0.21 on my portage tree) I got the same loop bug of the previous versions.

Exactly like for the previous version the problem regards an infinite loop generating when unmasking a package and it’s caused by not understanding the PortageXS function getArch(). To avoid the problem and using this wonderful tool without PortageXS it’s possible to manually set the arch on the bin file.

Just open it with your favorite editor as Root
su
vim /usr/bin/autounmask
Then find this line
my $arch = $pxs->getArch();
comment it and add this other
my $arch = 'amd64';
obviously replacing amd64 with your arch.

#!bin bash
apple=`emerge --sync && layman -S && update-eix && emerge -D world && revdep-rebuild`
An $apple a day keeps the doctor away