It recently came to my attention that WowAce and CurseForge were displaying old versions of my custom addon license. When I tried to update it, I discovered why that is -- submitting the form on the "edit license" page doesn't actually do anything 2/3 times, and the page continues to display the old text. It finally updated on the 3rd attempt.
There no longer seems to be any way to report issues on the site itself, so here's a forum thread.
Translation: We're no longer doing any development work whatsoever on the current CurseForge framework, concentrating instead on its replacement. Our current ETA to get everything onto the new stack is by End of Year; we need to add certain things like the pages and localization systems. The packager and other various subsystems are already in place.
Hmm, interesting Torhal. I'll check it out in depth later. I do have one request for the pkgmeta, and that there is both a file-deleted and folder-deleted entry, or something named appropriately.
What I have learned about people using no-lib-strip installs of AddOns is that occasionally an author discovers a dependency that can't be stripped out. Fine, we update the ToC and pkgmeta accordingly.
However, the end user, when he/she updates via the Curse Client, will still have a copy of the dependency installed.
I am asking for a way for authors to specify "if no other AddOn installs DependencyX in no-lib-strip, then delete it as standalone when MyAddOn gets updated".
Is this something that can be done? I checked the pkgmeta Wiki, and best I saw was move-folders, but that do the trick.
I'm not sure of the feasibility of something like that, but it's something that can be revisited after the first of the year. The whole move-folders thing has been reworked - in the old version, it was executed and then dependencies were brought in. Now, it brings in dependencies THEN moves folders per specification.
Will Curse no longer be offering code hosting and issue tracking, or are those features just not popular in the Wildstar community? I looked through 20-30 projects and found many linking to GitHub or Google Code, but no sign of any on-site repositories or issue tracking.
A lack of on-site code hosting isn't that big of a deal for me -- the only addons I develop in Curse-hosted repositories are those that were already established before I took them over, and I can easily move them -- but it will likely be a bigger issue for many other authors. And it seems like a short-sighted move on Curse's part, as you'd be driving everyone who prefers SVN (I've tried Git, I really have, and I still hate it) over to WoWInterface.
Since you mentioned the packager, though, does that mean that the "external repository" feature will actually work, or -- if the current feature works -- have some documentation explaining how to set it up correctly?
A lack of on-site issue tracking would be a pretty big downgrade, though. It's hard enough to get users to report bugs in a ticket on Curse instead of a comment on Curse... even though I have comments disabled on all my addons, and my profile explicitly says to not PM me about addon issues, I still get PMs about addon issues from users who are too stupid to submit a ticket (or read anything at all, apparently). If I'm going to have to ask such users to go register on a completely separate site to submit a ticket, I might as well just write "NO SUPPORT PROVIDED HERE" at the top of the page and give up entirely.
This is why we haven't brought WoW over to the new system yet - with all the features it's had over the years, it would be silly to have done so sooner.
As for the external repository feature: That's exactly what WildStar is using right now, via webhooks; pushing to the repo sends an API request to CurseForge, which triggers a pull/update and packaging.