If I were writing a script designed to work with either mysql-async or oxmysql, is there a way to write that dependency in the fxmanifest or do I need to provide multiple fxmanifest files?
Sadly, there’s no ‘or’ stuff at all at this time, but technically you could manually implement dependency stuff in an early-executing script (and add both resources’ @ files). I don’t get why oxmysql doesn’t use provide to be compatible with mysql-async scripts, though… this is exactly why provide was added.
Similarly, and this would be the cleanest method, you could make two ‘adapter’ resources, e.g. schwimsql-oxmysql and schwimsql-mysql-async and have that one provide 'schwimsql' and contain an include file that wraps the respective library’s API.
This seems to be the point where I’ve gotten stuck. How do I wrap m-a’s api? Does anyone know of another resource that does that that I could look through?