Add installation instructions

[ChocolateLoverRaj]

Fixes #10

[alba4k]

Why isn't this merged?

[alba4k]

That was fast, lol

by the way, @ChocolateLoverRaj , would you recommend using this? is it safe / done as it is? if so, I wouldn't mind creating an aur package for it if it's fine by you

[ChocolateLoverRaj]

@ChocolateLoverRaj , would you recommend using this?

I would recommend using this if people want to run PAM modules in parallel within a single PAM module (such as for sudo authentication). If they can directly run multiple PAM modules in their own code, such as what KDE and GDM do for lock screens, that would be better.

is it safe

It is hacky. See #3. Kind of like [pam-fprint-grosshack](https://gitlab.com/mishakmak/pam-fprint-grosshack)

done as it is?

Yes. It is ready to be used.

if so, I wouldn't mind creating an aur package for it if it's fine by you

That is fine with me. If you want you can add one of those tables of packaging status to the README too.

[alba4k]

I would be fine with it being like fprint-grosshack, as that is what I was using before. Will wait for some extra insight into #12 before adding this to the AUR

Wouldn't make a packaging tablet like that, just mention that it is avaiable as an aur package. also, is there any reason why the file name is libpam_any.so and not pam_any.so? is that how things are on fedora? I would likely rename it to pam_any.so on arch if there is no reason to keep it otherwise

[ChocolateLoverRaj]

is there any reason why the file name is libpam_any.so and not pam_any.so?

It's just the default Rust output file name. Probably caused by

pam-any/Cargo.toml

Line 7 in e776877

crate-type = ["cdylib"]

. This can be changed.

[alba4k]

Check what fedora uses for that kind of stuff first I guess, but otherwise sure