AGPLv3.0 license

[hgaiser]

Hey, cool project! I was looking for a crate that could handle Heroic game parsing for my application: https://github.com/hgaiser/moonshine

At the moment I can't because my application is licensed under BSD-2 so the two are incompatible. Would you be open to dual licensing this library with a more permissive license? I guess technically that would mean you'd need permission from the three contributors to this repo, no idea how tricky that would be.

Anyway, was just wondering if this is a possibility.

[Rolv-Apneseth]

Thank you, and moonshine seems like a really cool Moonlight client. I'll have to check it out next time I'm trying to setup remote gaming.

I think to be honest my first reaction would be no, I'm not really willing to dual-license this project - but I'll take some time to think about it. I've generally preferred to have my personal projects copy-left but I'm certainly not opposed to permissive licenses.

---

Just want to check though - are you sure this crate will suit your needs if you need to have (I'm assuming) this kind of a structure:

[[application_scanner]]
type = "heroic"
command = ["/usr/bin/xdg-open", "heroic://launch/{source}/{app_id}"]

The exported Game struct does expose the exact source (e.g. SupportedLaunchers::HeroicGog) but there's no directly exposed app_id - just a launch_command of type std::process::Command. I'm not sure if you can extract the arguments passed to that. This approach hasn't been a problem so far because this library has been used primarily by rofi-games, but just wanted to check if that would actually work for you even if I did dual-license it.

[hgaiser]

Thanks for considering, I would of course appreciate it but I also completely understand if you don't want to change the license.

Just want to check though - are you sure this crate will suit your needs if you need to have (I'm assuming) this kind of a structure:

Hmm I think this will be fine. It will indeed be configured roughly like how you said, but the command option will likely disappear and replaced with launch_command from your library.

[Rolv-Apneseth]

@chadkouse and @Rayzeq, since you've both contributed, any opinions? It doesn't matter if I decide I'm OK with this if either of you are not.

[Rayzeq]

Yeah I'm perfectly fine with it

[Rolv-Apneseth]

Just waiting on @chadkouse then. I'm leaning towards going ahead with the dual license if they agree.