RegalPotoo

"The apple doesn't fall far from the tree", but most apple seeds don't grow where they are dropped - they are carried away by birds or rodents and seed elsewhere. Also, most apples aren't true to seed anyway - plants grown from seed don't bear the same fruit

Saw a truck around town today with a ridiculous lift kit and chunky off-road tires that were clearly much larger than factory standard, and it got me thinking; if you install this kind of modification in a car, do you need to adjust the speedometer to compensate? What about the odometer?

My logic is the only absolute measurement the car has is how fast the wheels and drive shaft are turning, so presumably there is some sort of multiplier - 1 revolution = X meters - that is then used to show speed and track distance travelled, but that factor would need to change if the circumference of the tires did

The KDE 6 announcement says that

On prior versions you chose between either password or fingerprint authentication for the lockscreen. In Plasma 6, both are supported at the same time.

I've updated my Neon install, what do I need to do to enable this? I've set up a fingerprint through the user settings, but when the screen is locked I still have to use my password to unlock - there isn't a prompt, and touching the reader doesn't seem to do anything

Edit: follow up on an old post in case someone stumbles across it - I needed to install libpam-fprintd

I'm trying to find a thing, and I'm not turning up anything in my web searches so I figure I'd ask the cool people for help.

I've got several projects, tracked in Git, that rely on having a set of command line tools installed to work on locally - as an example, one requires Helm, Helmfile, sops, several Helm plugins, Pluto, Kubeval and the Kubernetes CLI. Because I don't hate future me, I want to ensure that I'm installing specific versions of these tools rather than just grabbing whatever happens to be the latest version. I also want to ensure that my CI runner grabs the same versions, so I can be reasonably sure that what I've tried locally will actually work when I go to deploy it.

My current solution to this is a big ol' Bash script, which works, but is kind of a pain to maintain. What I'm trying to find is a tool where I:

• Can write a definition, ideally somewhere shared between projects, of what it means to "install tool X"
• Include a file in my project that lists the tools and versions I want
• Run the tool on my machine and let it go grab the platform- and architecture- specific binaries from wherever, and install them somewhere that I can add to my $PATH for this specific project
• Run the tool in CI and do the same - if it can cache stuff then awesome

Linux support is a must, other platforms would be nice as well.

Basically I'm looking for Pythons' pip + virtualenv workflow, but for prebuilt tools like helm, terraform, sops, etc. Anyone know of anything? I've looked at homebrew (seems to want to install system-wide), and VSCode dev containers (doesn't solve the CI need, and I'd still need to solve installing the tools myself)

A whole bunch of this sounds really familiar for some reason...