Not sure what you are doing. First you need to synchronise with the Portage ebuild repository, which will download all the latest ebuilds automatically to your PC:
- Code: Select all
emerge --sync
Then you need to synchronise with the Sabayon ebuild overlay, which will download all the latest Sabayon overlay ebuilds automatically to your PC:
- Code: Select all
layman -S
Then the latest ebuild of evdev will be in the directory I mentioned in my previous post. Is that the case? Have you looked to see if the ebuild file is in the directory /usr/portage/x11-drivers/xf86-input-evdev/? And what message was displayed when you entered the command to generate the manifest after you had updated the source code tarball in the /usr/portage/distfiles/ directory?
EDIT: If xf86-input-evdev-2.3.2 is not in the repository yet, but you see xf86-input-evdev-2.3.1 is there, then perform the procedure for version 2.3.1 instead of 2.3.2. I notice from the package list in the Press Release for SL 5.1-r1 that the version of evdev shipped with SL 5.1-r1 is evdev-2.3.0, so try the procedure for 2.3.1 if 2.3.2 is not in the repository yet (but you still should check what's in the directory /usr/portage/x11-drivers/xf86-input-evdev/).