@Adirelle: as the curse client makes me gag - I'm just a little too old school - is the mechanism it's using documented anywhere. Or is it basically generating a dummy addon complete with .toc & .xml files?
@orionshock: I have no plans to run alpha libs. My point was I can't easily tell what the latest beta+ versions are. If whatever is on curse truly is the latest stable versions & that's addon devs are embedding in their code then great, but that doesn't seem likely. I can look for version tags inside individual lib/.../... files to check that but I was hoping for a simpler approach.
Hijacking this thread ever so slightly (mostly because that seemed better than starting a new one)....
Are their stand-alone packagings - either on wowace or curse - of the core Ace3 libs or the various others consistently used by addons that would allow me to install them separately? The latest version of Ace3 on curse, for example, is dated from April yet I know there are alpha releases that are less than 48 hours old and I don't want to introduce new issues but back-revving libraries unintentionally.
I ask because I'm trying to track down what is causing me massive FPS loss while raiding and I can't get meaningful CPU breakdowns if the first addon to use a bunch of embedded libraries gets tagged for the totality of the CPU utilisation. If I can force the libs to load first via a separate, lib-only addon, then I can at least see *exactly* what is driving CPU utilisation etc and provide useful feedback to the author of whatever code is causing me issues.