We took a step forward and moved CallbackHandler-1.0 from Ace3 into its own project and repository, while the old SVN URL would still work, its suggested to use the following:
Please make sure to validate all your externals and don't hesitate to contact us either on IRC, through the forums or the "Report Project" feature on the page itself.
Some automatic processing have been done (by ckknight I think) to update the externals and create a .pkgmeta, but there are still some flaws.
Here are some things to know and to check :
the svn:externals point to the new repositories, e.g. svn://svn.wowace.com/somepath,
the .pkgmeta externals points to the old, read-only repositories, e.g. http://svn.wowace.com/wowace/somepath but this server has been renamed, it is now http://oldsvn.wowace.com/wowace/somepath. Alternatively, you could fix them to points to the new repositories.
Ensure that no .pkgmeta external path start with "/", or the file will not pass the pre-commit hook check.
The .pkgmeta externals require a colon ":" after the path, in contrary to svn:externals.
As Adirelle pointed out, the auto-generated .pkgmeta file will probably NOT work correctly.
Please update your .pkgmeta file accordingly, you can find the proper URLs for the libraries on their project page. If you seem to be unable to find a library that you used before, please notify me!
Thanks Orion, I've put in a report since I can't find what I'm suppose to do to claim a project. As for IRC, I tried the instructions on Wiki in the past but was never able to log to the freenode server. If I remember correctly, the server was asking for login information that I was unable to provide and got disconnected from the server almost immediately. I guess I'll have to try again.
As for IRC, I tried the instructions on Wiki in the past but was never able to log to the freenode server. If I remember correctly, the server was asking for login information that I was unable to provide and got disconnected from the server almost immediately. I guess I'll have to try again.
I saw that a while ago but since I got disconnected from the server pretty much as soon as I got in, there was no way for me to change channel to #wowace nor to register my nick. Both being able to
Like I said, it's been quite a while since last I tried so I'll have to try again.
I'm used to checking out the projects i work on directly in my interface folder with externals (as i have all my addons with externals embedded). However, now with the new .pkgmeta, there will not be any externals anymore in the projects i check out. I know that i can just add the externals as before (limited to SVN of course, but that's all i use, at least for now), but it feels quite silly to have them in two places. So i was just wondering how you manage your projects when you develop in-game? I like the ability to just hack while playing, then after that, just submit the changes.
I'm used to checking out the projects i work on directly in my interface folder with externals (as i have all my addons with externals embedded). However, now with the new .pkgmeta, there will not be any externals anymore in the projects i check out. I know that i can just add the externals as before (limited to SVN of course, but that's all i use, at least for now), but it feels quite silly to have them in two places. So i was just wondering how you manage your projects when you develop in-game? I like the ability to just hack while playing, then after that, just submit the changes.
(and don't tell me i should run dis-embedded...)
I'm not sure if I'm doing it right myself (by right I mean easiest and sure to not break anything). What I do is setup the .pkgmeta file the way I want it, manually create my libs folder and copy into it the libs I want there, ignore the libs folder via svn, code and test. Once I get an alpha zip I test that and then tag for release/beta. Once and a while when I'm testing the alpha zip I'll copy the libs folder out of that into my working copy so I have decently updated libs there.
Something else that might be worth mentioning (since I've seen it in a few packages), the .pkgmeta files can't have tabs in their whitespace. This is explicitly disallowed by the YAML spec and breaks most YAML parsers.
Something else that might be worth mentioning (since I've seen it in a few packages), the .pkgmeta files can't have tabs in their whitespace. This is explicitly disallowed by the YAML spec and breaks most YAML parsers.
iirc we... added the ability. so its not 100% YAML.
The auto-generated .pkgmeta file for one of my projects errors on exporting with an error text of :
No repository found in 'svn://svn.wowace.com/wow/gratuity-lib/mainline/trunk/Gratuity-2.0'
So it looks like it generated an incorrect .pkgmeta for this library.
The library is fine, however some library paths were changed afterwards and need adjustments. Just change your .pkgmeta and externals to say "gratuitylib" instead of "gratuity-lib" and it will be fine.
As a general guideline, we removed all inappropriate dashes from library names, so we have a consistent naming scheme now
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderatortogether with the WoWAce Transition we did some other steps to get a cleaner layout.
LibStub
The LibStub repo is actually called libstub and not lib-stub, so you may need to adjust your externals there.
Proper Syntax for LibStub would be:
CallbackHandler-1.0
We took a step forward and moved CallbackHandler-1.0 from Ace3 into its own project and repository, while the old SVN URL would still work, its suggested to use the following:
Ace3
There didn't change much about how to use Ace3, just as a reminder, some example entrys for .pkgmeta
All other library repositories should be in a consistent path layout like this:
[tt]svn://svn.wowace.com/wow/<name>/mainline/trunk/<path>[/tt]
<name> is the "old" directory name of the library, in all lower case and dots replaced by dashes.
<path> is the same path as before.
For Example, if you had http://svn.wowace.com/wowace/trunk/LibSink-2.0/LibSink-2.0 it now becomes svn://svn.wowace.com/wow/libsink-2-0/mainline/trunk/LibSink-2.0
----
Please make sure to validate all your externals and don't hesitate to contact us either on IRC, through the forums or the "Report Project" feature on the page itself.
Link to the .pkgmeta tutorial:
http://www.wowace.com/knowledge-base/pkgmeta-file/
- Nevcairiel
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHere are some things to know and to check :
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorPlease update your .pkgmeta file accordingly, you can find the proper URLs for the libraries on their project page. If you seem to be unable to find a library that you used before, please notify me!
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumsvn://svn.wowace.com/wow/libbabble-faction-3-0/mainline/trunk
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorFor Example, LibSink-2.0:
The new name is all lowercase, and the dot converted to a dash, so now its libsink-2-0
All repositories can be reached by svn://svn.wowace.com/wow/<project>/mainline/trunk
Make sure to append any sub-path inside the repository to the end of the link for your externals, for example for LibSink-2.0 it would be:
svn://svn.wowace.com/wow/libsink-2-0/mainline/trunk/LibSink-2.0
or for LibBabble-Boss-3.0
svn://svn.wowace.com/wow/libbabble-boss-3-0/mainline/trunk
If for any reason ANY library does not work, please don't hesitate to contact me, and i'll get it fixed as soon as possible.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumFirst thing, thanks all for the humongous effort that you all put in the site and the transition :-).
How do I proceed to be made project leaders for my projects? Is there a place where I need to open a ticket or what not?
Before someone suggest it, no, I will not put my email address in a .toc text file that can be farmed by every spam-bot out there.
TIA
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumRegister your nick?
http://forums.wowace.com/showthread.php?t=1287&page=3
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI saw that a while ago but since I got disconnected from the server pretty much as soon as I got in, there was no way for me to change channel to #wowace nor to register my nick. Both being able to
Like I said, it's been quite a while since last I tried so I'll have to try again.
(and don't tell me i should run dis-embedded...)
I'm not sure if I'm doing it right myself (by right I mean easiest and sure to not break anything). What I do is setup the .pkgmeta file the way I want it, manually create my libs folder and copy into it the libs I want there, ignore the libs folder via svn, code and test. Once I get an alpha zip I test that and then tag for release/beta. Once and a while when I'm testing the alpha zip I'll copy the libs folder out of that into my working copy so I have decently updated libs there.
iirc we... added the ability. so its not 100% YAML.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe auto-generated .pkgmeta file for one of my projects errors on exporting with an error text of :
No repository found in 'svn://svn.wowace.com/wow/gratuity-lib/mainline/trunk/Gratuity-2.0'
So it looks like it generated an incorrect .pkgmeta for this library.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorThe library is fine, however some library paths were changed afterwards and need adjustments. Just change your .pkgmeta and externals to say "gratuitylib" instead of "gratuity-lib" and it will be fine.
As a general guideline, we removed all inappropriate dashes from library names, so we have a consistent naming scheme now