The problem is that devs don't tag (at all, or not often enough), not that they tag broken versions as beta.
The second problem is that alot of addons use trunk versions, and thus your attempts to use a stable version are futile due to auto-upgrading.
Two things should happen:
1) Addons should use tag:latest on most libraries.
2) Devs should make sure to have a semi-recent tag of their addon.
Another problem that occurs from this issue is with disembedding.
Assuming you run all release versions of your addons, you will also only get release versions of the libraries.
Now, if the addon uses trunk, it'll have the latest version of the lib, but if the user dis-embeds, he'll get the last release version of it, unless he manually sets the curse client to "alpha" for that library.
I just would like to point out that the core issue here is the concept of embedding. The number of issues, little or big, that are caused by the whole "embedding" idea, for me, should make the community think again about enforcing it.
I just would like to point out that the core issue here is the concept of embedding. The number of issues, little or big, that are caused by the whole "embedding" idea, for me, should make the community think again about enforcing it.
What would be the alternative. Embedding is a product of the current hegemony - that's pretty difficult to change.
The problem with these threads is that no one seems to have enough teeth or balls to enforce anything that is concluded. IMO this entire discussion is rather pointless unless one of you is willing to put foot to ass and do something about it.
but isn't that exactly what this thread is about changing how libs are handled? if true and we want to actually do it then the defaults would be the first thing that should change otherwise this problem will always be here because new authors, lazy authors, and authors that don't read will never use the right system
The problem with these threads is that no one seems to have enough teeth or balls to enforce anything that is concluded. IMO this entire discussion is rather pointless unless one of you is willing to put foot to ass and do something about it.
Are you saying I need to become active in the community again?
This is a community, if you are part of this community then you should be participating in it. We have talked and talked and talked for years about these sorts of changes. All the core lib authors are usually active & available so this change shouldn't be a surprise to any of them. The rest of them are mostly on community life support.
However, the change would require that libraries are actually tagged properly. And i don't think most of the common used libraries actually are.
Yeah and half of those were probably maintained by me at some point. And I'm one of the people that can and will harass people until they start doing something right or just change it myself.
But alas I have departed from developing for WoW and thus no longer have anything to do with the inner workings of the community, unless I'm bored.
Pardon me, but I am confused. The tag: latest does not get the latest file, but instead gets the last public release or beta? That seems a tad backward. Unless I read that wrong.
The external definitions don't operator on the concept of "files", they read the source repository directly. Once you define any kind of "tag" in the external definition, it'll only look for tags. "latest" is a magic tag that will automatically get the newest tag that exists.
While the idea of making .pkgmeta externals grab the latest tag, instead of the latest revision, by default is a good one, I'm slightly puzzled as to why addon authors are tagging versions of their addons with broken libraries in the first place. If you're developing an addon that uses libraries, and you set up your .pkgmeta to grab the latest revisions of those libraries, why are you not keeping your local copies of those libraries up to date?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorThe problem is that devs don't tag (at all, or not often enough), not that they tag broken versions as beta.
The second problem is that alot of addons use trunk versions, and thus your attempts to use a stable version are futile due to auto-upgrading.
Two things should happen:
1) Addons should use tag:latest on most libraries.
2) Devs should make sure to have a semi-recent tag of their addon.
Another problem that occurs from this issue is with disembedding.
Assuming you run all release versions of your addons, you will also only get release versions of the libraries.
Now, if the addon uses trunk, it'll have the latest version of the lib, but if the user dis-embeds, he'll get the last release version of it, unless he manually sets the curse client to "alpha" for that library.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWhat would be the alternative. Embedding is a product of the current hegemony - that's pretty difficult to change.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumthat would be the proper way to fix it imo (would encourage more tagging by lib authors as well)
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumbut isn't that exactly what this thread is about changing how libs are handled? if true and we want to actually do it then the defaults would be the first thing that should change otherwise this problem will always be here because new authors, lazy authors, and authors that don't read will never use the right system
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premiumexternals: # Pull latest alpha libs/LibSharedMedia-3.0: svn://svn.wowace.com/wow/libsharedmedia-3-0/mainline/trunk/LibSharedMedia-3.0 # Pull latest beta/release libs/LibHealComm-4.0: url: git://git.wowace.com/wow/libhealcomm-4-0/mainline.git tag: latestTo something like this:
externals: # Pull latest alpha libs/LibSharedMedia-3.0: url: svn://svn.wowace.com/wow/libsharedmedia-3-0/mainline/trunk/LibSharedMedia-3.0 tag: alpha # Pull latest beta/release libs/LibHealComm-4.0: git://git.wowace.com/wow/libhealcomm-4-0/mainline.git-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAre you saying I need to become active in the community again?
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorHowever, the change would require that libraries are actually tagged properly. And i don't think most of the common used libraries actually are.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis is a community, if you are part of this community then you should be participating in it. We have talked and talked and talked for years about these sorts of changes. All the core lib authors are usually active & available so this change shouldn't be a surprise to any of them. The rest of them are mostly on community life support.
Like Cartographer-2, let them die.
Yeah and half of those were probably maintained by me at some point. And I'm one of the people that can and will harass people until they start doing something right or just change it myself.
But alas I have departed from developing for WoW and thus no longer have anything to do with the inner workings of the community, unless I'm bored.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator-
View User Profile
-
View Posts
-
Send Message
Forum Moderator