Two questions: If you look at SmartRes on Curse, the d/l file is 6.02 which is correct, but if you read the project details it still says 5.11 which means it hasn't shown up under Updated Addons. How do I fix this? It has always just picked the name from what I call the file at WowAce.
Second, people who use the Curse Client and have it set to load libs seperately have no issues, but manual downloaders or people who don't use that feature are reporting that some files are missing, especially SharedMedia-1.0
SR is Ace2, and I tried changing the .pkgmeta for latest versions of the files, and that didn't work.
So, um, at this point, I'm lost, and ran out of ideas.
And as for the .pkgmeta/toc, thank you for that. Will that continue to work if I use the tag: latest in the .pgkmeta?
Your .pkgmeta looks fine, but since I don't use CurseForge repos I don't have much first-hand experience with the CurseForge packager. All of the libraries you're embedding are quite old, and are unlikely to see many (if any) changes, so in your case just pulling from the trunk is probably okay. If you upgrade to, say, Ace3, then you would probably want to pull from a tag (even if just "latest") rather than from the trunk.
Either way though, the libraries were getting embedded, so there's nothing techincally wrong with your .pkgmeta. They just weren't being loaded by WoW because the references to them in the TOC were commented out even in the zip with embeds.
Hmmm so a newer beta can't overwrite an older release? Weird, but thanks for the help.
I think the Curse addon page only shows the latest release version. And I'd bet it only proposes you to download the latest release too. For the beta versions you have to scroll down the page to select them in the list.
As for the Curse Client, it installs only releases by default. As Torhal said, users have to enable beta (or even alpha) downloads.
@phanx, the WoWAce and CF Packagers are in fact the same program/service (iirc)
I've seen the curse client refuse to "automatically" revert a package from beta|alpha back to release. Ie: one selects the automatic install of a beta file from CF/WA project files, while CC is only doing releases. You'll have to select it specifically and reinstall it to get CC to revert it to a release from beta|alpha.