aftman

aftman copied to clipboard

marcusleonas

Failed to find compatible OS

2

I tried using Aftman to install a pixelfix, but I just couldn't install this one because it says "win" because of "windows"... https://github.com/Corecii/Transparent-Pixel-Fix/releases/tag/1.0.0

KelvenOne

Getting "...Error while loading shared libraries: libssl.so.1.1..." on WSL Ubuntu

3

I've been trying to use install aftman on my ubuntu WSL system using the provided binary for linux. I unzip the linux file and attempt to run `./aftman self-install`, and...

Jeffimenson

System is `windows-x64`, Aftman downloads `linux-arm64` because the asset for `windows-x64` doesn't exist. It should instead error if the correct asset isn't detected.

hoontee

Improved error messages when Rosetta is not installed

2

When running an executable built for x86 on an M1/M2 mac you will get this confusing error message if Rosetta is not installed: `Bad CPU type in executable` Since aftman...

filiptibell

Cannot use tools with Aftman when Foreman is already managing them

2

I have some projects that use Foreman, and when trying to install the same tools via Aftman I run into issues where Foreman is still trying to invoke those tools....

vocksel

How do I uninstall Aftman?

5

I'm probably stupid but I can't figure out how to install Aftman as I prefer Foreman, but I don't know how to just get rid of it off my computer...

starrstrux

MacOS aarch Release build is actually x86

1

When I download [aftman-0.2.7-macos-aarch64.zip](https://github.com/LPGhatguy/aftman/releases/download/v0.2.7/aftman-0.2.7-macos-aarch64.zip) from the v0.2.7 release page and run file on it I get `aftman: Mach-O 64-bit executable x86_64` When I build it locally I am getting `aftman:...

thunn

Rather than placing the `.aftman` folder directly into `HOME`, I'd much prefer if it tried out the `XDG_DATA_HOME` environment variable first, **then** fall back to `HOME`. It may also be...

4xMSAA

fix install from failing with different /tmp filesystem

8

fixes #35 This changes the `fs_err::rename()` function from a (likely unintended) use case to `fs_err::copy()` instead, which supports multiple filesystems in an operation.

Joshument