allow parameters to be specified in any order

[javier-lopez]

Been testing a little, static-get -p /tmp/opt -i htop works great, but specifying the parameters in a different order doesn't work:

❯ ./static-get -i htop -p /tmp/opt              
Option '-p' requires a parameter -p   

---

I get the same issue using the other possible options (such as -d), perhaps it's an issue with how the arguments are handled?

The accepted PR should fix this behaviour and add test coverage.

[hrshbh]

According to the ./static-get --help, usage is ./static-get [OPTION]... PACKAGE..., therefore

./static-get -i htop -p /tmp/opt

is wrong according to the --help because htop is not the last argument in the command, but

./static-get -i -p /tmp/opt htop

or,

./static-get -p /tmp/opt -i htop

are correct.
The programs we want to download or install (here htop) are not associated with any option (here -i).
Therefore I think program is working good and agrees with what is mentioned in the usage section.
What might be needed is adding a check to produce a better error message.
@javier-lopez Am I right?

[javier-lopez]

Hello @Hrishabh23 ,

Thank you for taking the time to contribute to minos-static 😀 , although what you say is correct, I think some users (me included) would prefer that the tools adapt to ourselves and not the other way around, I think static-get should be able to parse the arguments in almost any way possible, unless such policy jeopardize the main goal itself, so to answer you question, I'll prefer we modify the tool and then the README.md to clarify we can include the package in any order.

[hrshbh]

Sure, I understand what your point is there.
I am going for it.