search

gorilla-devs / ferium

Fast and multi-source CLI program for managing Minecraft mods and modpacks from Modrinth, CurseForge, and GitHub Releases
Mozilla Public License 2.0
1.15k stars 49 forks source link

Dry-runs, an upgrade confirmation prompt, and an option to view the changelog #49

Open JustSimplyKyle opened 2 years ago

JustSimplyKyle commented 2 years ago

yeah, this will be helpful. Also, would it be possible to NOT do this on first download, because that would certainly print out a lot of unreadable stuff. Instead, print it when upgrading mods.

theRookieCoder commented 2 years ago

But this would just print out the changelog of the latest version? It wouldn't actually print the changes made since the version that was previously installed. And should this be normal behaviour, or an opt-in through a --verbose flag?

JustSimplyKyle commented 2 years ago

--verbose Yes, just the latest version would be enough Also, it would be great if this behavious can be enabled in config, instead of having to pass the --verbose time every time

theRookieCoder commented 2 years ago

it would be great if this behavious can be enabled in config

Sure I'll do that then

theRookieCoder commented 2 years ago

would it be possible to NOT do this on first download

How would this be done though? I guess it's the same issue with figuring out the mod from the file

JustSimplyKyle commented 2 years ago

Ah yes the age old problem I guess it's ok to print out the first download Since it's not that big of an issue

theRookieCoder commented 2 years ago

How would this be implemented for GitHub Releases? They only have the release description right?

JustSimplyKyle commented 2 years ago

Yep, normally release description are served as small changelogs

theRookieCoder commented 2 years ago

As this Redditor suggested, we can also ask the user on whether to update or not (like most Linux package managers). And of course a --force option for automatic upgrades