Support older versions of macOS

[ok-coder1]

Does it work with older versions of macOS?

I am using macOS Sierra 10.12.6.

The latest version does not work.

[theRookieCoder]

Can you describe what you mean by "it doesn't work".

[ok-coder1]

Ferium v4.7.0 on macOS 10.12.6: dyld: cannot load 'ferium' (load command 0x80000034 is unknown)

[theRookieCoder]

This will require some changes in the build action. For now, you can compile it from source to make it work.

[ok-coder1]

Compiling from source is hard and slow. What is the approximate ETA for this to get fixed?

[ok-coder1]

There's no PR open yet. @theRookieCoder, is this fixed?

[theRookieCoder]

Please be patient @ok-coder1. I'm a final year high school student who's quite busy with academics, I have exams going on at the moment too. I might not be able to get a fix this weekend either.

Compiling from source is hard

It's not that hard with Rust, just run curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh to install the toolchain, then run cargo install ferium to download the source code and install the program. Sure it's not that fast, but it should get you up and running <30 mins.

[ok-coder1]

I'm a final year high school student who's quite busy with academics, I have exams going on at the moment too.

Oh, sorry.

[ok-coder1]

It's not that hard with Rust, just run curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Well running curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh spat out this error: curl: (35) Unknown SSL protocol error in connection to sh.rustup.rs:-9836.

[ok-coder1]

It's not that hard with Rust, just run curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Well running curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh spat out this error: curl: (35) Unknown SSL protocol error in connection to sh.rustup.rs:-9836.

[ok-coder1]

It's not that hard with Rust, just run curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh to install the toolchain, then run cargo install ferium to download the source code and install the program. Sure it's not that fast, but it should get you up and running <30 mins.

Crate [email protected] does not build as it needs macOS 10.13, but I have macOS 10.12.6.

[ok-coder1]

It's been more than 2 months, any update?

[Nekkowe]

Your best bet is switching to an operating system that's still being actively maintained.
Sierra is not receiving security patches anymore (as of December 2019). It's not safe to use.

macOS Sierra is over seven years out of date, and macOS in general is a pain to develop for at the best of times. Only a vanishingly small number of people still use Sierra and would benefit from the work required to get ferium running on it. And if a depencency (like ring, apparently) is dependent on a later version of macOS, it could take a lot of time and effort to get & keep ferium working on your version of mac.

You might be out of luck here. This is just my personal opinion, but I don't think it's reasonable to expect someone else to invest time into getting this working on Sierra for - in all likelihood - just you alone.

I don't know your situation, but it looks to me like you should absolutely either switch to an up-to-date version of macOS, or move to a different operating system altogether.

[ok-coder1]

switch to an up-to-date version of macOS

The latest I can upgrade to officially is 10.13, which has also reached is end-of-life.

move to a different operating system altogether

I could, but that's not possible. (Boot Camp is only for Windows 7/8 on my macOS, and anyways I don't have enough storage space for it)

Using Virtual Machines might be possible, but the frame rate will be around 2 FPS.

[theRookieCoder]

Rustup seems to have had the same issue, lowering the deployment target in their CI worked for them. I will try that too.

[theRookieCoder]

@ok-coder1 could you test this build https://github.com/gorilla-devs/ferium/actions/runs/11402652147/artifacts/2073737987

[ok-coder1]

@ok-coder1 could you test this build https://github.com/gorilla-devs/ferium/actions/runs/11402652147/artifacts/2073737987

Users-iMac:~ User$ cd Downloads/
Users-iMac:Downloads User$ cd binaries-macos-latest
Users-iMac:binaries-macos-latest User$ ls
ferium			ferium-macos-arm.zip	ferium-macos-x64.zip
Users-iMac:binaries-macos-latest User$ ./ferium 
Fast CLI program for managing Minecraft mods and modpacks from Modrinth, CurseForge, and Github Releases

Usage: ferium [OPTIONS] <COMMAND>

Commands:
  add       Add mods to the profile
  scan      Scan the profile's output directory (or the specified directory) for mods and add them to the profile
  complete  Print shell auto completions for the specified shell
  list      List all the mods in the profile, and with some their metadata if verbose [aliases: mods]
  modpack   Add, configure, delete, switch, list, or upgrade modpacks
  modpacks  List all the modpacks with their data
  profile   Create, configure, delete, switch, or list profiles
  profiles  List all the profiles with their data
  remove    Remove mods and/or repositories from the profile. Optionally, provide a list of names or IDs of the mods to remove [aliases: rm]
  upgrade   Download and install the latest compatible version of your mods [aliases: download, install]
  help      Print this message or the help of the given subcommand(s)

Options:
  -t, --threads <THREADS>
          Sets the number of worker threads the tokio runtime will use. You can also use the environment variable `TOKIO_WORKER_THREADS`
  -p, --parallel-network <PARALLEL_NETWORK>
          Specify the maximum number of parallel network requests to perform
      --github-token <GITHUB_TOKEN>
          Set a GitHub personal access token for increasing the GitHub API rate limit. You can also use the environment variable `GITHUB_TOKEN` [aliases: gh]
      --curseforge-api-key <CURSEFORGE_API_KEY>
          Set a custom Curseforge API key. You can also use the environment variable `CURSEFORGE_API_KEY` [aliases: cf]
  -c, --config-file <CONFIG_FILE>
          Set the file to read the config from. This does not change the `cache` and `tmp` directories. You can also use the environment variable `FERIUM_CONFIG_FILE` [aliases: config, conf]
  -h, --help
          Print help
  -V, --version
          Print version
Users-iMac:binaries-macos-latest User$ 

Looks like it worked! Thanks a lot!

[ok-coder1]

You could release this as a point update, like in rustup.

[theRookieCoder]

Well that was easier than I expected, hopefully it doesn't cause any other issues.

Fixed in d9a10176c0482296d85ca86fe52bbcc1d4d65d87

[theRookieCoder]

I don't think I will be dedicating a release to this, I have huge changes pending that I want to release together. Let me know if the CI build causes any issues in the meantime.

[ok-coder1]

I don't think I will be dedicating a release to this, I have huge changes pending that I want to release together. Let me know if the CI build causes any issues in the meantime.

Okay.

[ok-coder1]

Not released yet, so opening.

[ok-coder1]

Ferium does not remove through the ID for some reason now.

[theRookieCoder]

You are trying to remove a mod using its slug, that is not (and never was) supported.

[ok-coder1]

You are trying to remove a mod using its slug, that is not (and never was) supported.

WDYM never was? I remember removing a few mods using their slugs when I first got it to work.

[ok-coder1]

Actually, now that I think of it, I think I removed mods (probably one word ones like Sodium) using their name, not slugs.

[theRookieCoder]

I removed mods (probably one word ones like Sodium) using their name, not slugs.

Yes precisely, only removing by ID and name is supported.

[ok-coder1]

Can you please add this feature of removing mods using slugs?

[theRookieCoder]

#439

[ok-coder1]

#439

Thanks!