plata
plata
I'm not sure if this is possible. I would assume that it's probably easier to simply write a Phoenicis script manually.
Ok, but still I doubt that it will work 100% automatically. So maybe it would be better to have a simple converter. Then you could fix possible issues manually after...
@qparis just to get you right: You're idea is to implement this in Javascript? So derive `InstallerScript`? I think that could work. We would probably need a generic YAML parser...
Would you want to have a `LutrisDTO` or use the map directly?
Can you describe the steps which would be required to do this in a way that someone who doesn't know Phoenicis in detail could implement it?
A point we need to think about: what do we do about the Wine version? In general, the Lutris Wine version is not available (unless we include the Lutris Wine...
How can you find out if we have a similar build automatically?
@qparis is this still relevant? Or can we close it until someone complains?
We could certainly do that but I see no benefit. Why should anybody dare to think about a container name? It only makes using Phoenicis more difficult because you would...
There's one flaw with the proposal (but also with the current implementation): It is not guaranteed (by design) that application IDs are unique. Only the triple of type ID, category...