I'm running version 0.40-r1.. When I "emerge --search tp_smapi" portage says that 0.40-r1 is the latest version available...
The arch wiki talks about 0.41 so it shouldn't be that old?! Should I'll try to install the "tpacpi-bat" script from AUR? (download tarball and then..?! )

I'm running version 0.40-r1.. When I "emerge --search tp_smapi" portage says that 0.40-r1 is the latest version available...
The arch wiki talks about 0.41 so it shouldn't be that old?! Should I'll try to install the "tpacpi-bat" script from AUR? (download tarball and then..?! )

whenever an ebuild writer crafts an ebuild (the install files gentoo - specifically, portage - uses to do the compiling/install/etc), they will in essence "tag" that ebuild according to what architectures it's been tested against, and is known to run stable on.

the ebuilds your install will accept to be used are based, among other things, on how the ebuild has been tagged by the developer - in this case, based on what keywords you have configured portage to accept.

if my architecture is 'amd64', then by default, running "stable" gentoo, I will accept ebuilds that are tagged as 'amd64'
if I decide that I'm willing to use software from the testing branch, I can accept additional keywords. In the case of this ebuild, we have said that we will accept both 'amd64' and '~amd64', the latter being what ebuilds in the testing branch are tagged as.

I can either do that globally, or i can do that on a per-package basis.

Enabling an additional keyword on a per-package basis is what we have done with this package
Enabling an additional keyword globally entails adding ACCEPT_KEYWORDS="~amd64" to /etc/portage/make.conf (or /etc/make.conf, depending on which you use)

as to which is the best for you, there is no "one size fits all" rule.

Expect a handful of quirks if you enable ~amd64 (or, ~x86) globally.
Expect a colossal pain in the ass if you try to have half of your packages ~amd64, and half of them amd64 - unless you're really comfortable with portage
Expect things to be quiet if you run exclusively amd64
Expect things to be mostly quiet if you only very selectively unkeyword packages (as we've done here)

That is all a greatly simplified version of things. But it gets the basic point expressed.

LoTeK wrote:

and just to be sure, tp_smapi allow one to control things like charging the battery to a certain percentage, but it does not reduce power consumption?

I have absolutely zero idea. I haven't owned a thinkpad for a long while, and never used this module - i just googled a bit and found out the T420 requires a later version of tp_smapi _________________Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash