-
Notifications
You must be signed in to change notification settings - Fork 10
Open
Description
Hello!
You guys explicitly depend on ancient Mojolicious (here) that is two major versions behind the current one (at the moment of writing). Is there any specific reason for that?
Here's my install log, just in case:
$ cpanm Ethereum::RPC::Client
--> Working on Ethereum::RPC::Client
Fetching http://www.cpan.org/authors/id/B/BI/BINARY/Ethereum-RPC-Client-0.05.tar.gz ... OK
Configuring Ethereum-RPC-Client-0.05 ... OK
==> Found dependencies: Mojolicious
--> Working on Mojolicious
Fetching http://backpan.perl.org/authors/id/S/SR/SRI/Mojolicious-7.29.tar.gz ... OK
Configuring Mojolicious-7.29 ... OK
Building and testing Mojolicious-7.29 ... FAIL
! Installing Mojolicious failed. See /home/$USER/.cpanm/work/1687089645.190684/build.log for details. Retry with --force to force install it.
! Installing the dependencies failed: Installed version (9.22) of Mojolicious is not in range '== 7.29'
! Bailing out the installation for Ethereum-RPC-Client-0.05.
Currently using a separate perl for that btw.
Correct me if I'm wrong, but I have seen Mojolicious-related stuff only being used once throughout the entire codebase - here. As far as I know, there was no breaking changes to Mojo::UserAgent
's post()
since 7.x, perhaps it's safe to update the dependency version? Or - even better - get rid of Mojolicious dependency altogether since you're not using async stuff anyway?
Thanks!
Metadata
Metadata
Assignees
Labels
No labels