Authors CurseForge

Quote from beesknees »

I'm having trouble with addons not recognizing SpecialEventsAura-2.0, I think because of how SpecialEventsEmbed is being split.

I just uploaded a fix for this. Sorry I took so long to post it. I found this myself a couple days ago, but came down with a fever so never got around to posting it. You should manually remove any broken SpecialEventsEmbed_... files from your addon folder.

Let me know if this fix works for you.

The latest version fixed the problem with SpecialEvents.

I hope you're feeling better Nayala, and thanks for the fix!

Quote from beesknees »

The latest version fixed the problem with SpecialEvents.

Cool.

Quote from beesknees »

I hope you're feeling better Nayala, and thanks for the fix!

Thanks, and your welcome.

FYI, I just added another feature that allows archiving of addons for sharing with others. It should now be able to create .zip, .tar, .tar.Z, .tar.gz, .tar.bz2, .tgz, and .tbz files. If anyone has been trying to keep addons in sync across several computers this should make it easier.

I've recently run into troubles with how addonpkg installs the Ace2 set of libraries. Addonpkg splits up Ace2 separate addons called Ace2_##:

Ace2
Ace2_AceAddon-2.0
Ace2_AceComm-2.0
Ace2_AceConsole-2.0
Ace2_AceDB-2.0
Ace2_AceDebug-2.0
Ace2_AceEvent-2.0
Ace2_AceHook-2.1
Ace2_AceLibrary
Ace2_AceLocale-2.2
Ace2_AceModuleCore-2.0
Ace2_AceOO-2.0
Ace2_AceTab-2.0

I believe this is happening because addonpkg looks at the OptionalDeps line of Ace2 and sees these subpackages listed. The Ace2 toc file was recently changed and this OptionalDeps line added. Why it was added, I don't know.

The problem with splitting up the Ace2 library suite like addonpkg does is that the new addon listing is not consistent with all of the Dependencies listed in the Ace2_## toc files. For example, Ace2_Comm-2.0.toc lists

## Dependencies: AceLibrary, AceEvent-2.0, AceOO-2.0

not

## Dependencies: AceLibrary, Ace2_AceEvent-2.0, Ace2_AceOO-2.0

I can get around this by using addonpkg for all my other addons, and then copying Ace2 directory from the staging area rather than letting addonpkg "install" it, but it would be nice if you could fix it. :) Or should I instead be asking the Ace library maintainers why they changed Ace2.toc?

Quote from beesknees »

I've recently run into troubles with how addonpkg installs the Ace2 set of libraries. Addonpkg splits up Ace2 separate addons called Ace2_##:

I've uploaded a new version which should properly split the Ace2 library and many other LoD addons. Sorry that I haven't had more time of late to work on this.

Thanks for the fix! Works great. :D

Recently the LoD addons that were embedded in BigWigs got moved to separate folders. This caused the database that addonpkg uses to keep track of the components to be out of date. The fix is to remove the .addonpkg.addons file in your staging directory and then fetching BigWigs and any of the now separate addons you need.

Giving me these errors for all my addons when trying to -fetch.

subversion/libsvn_ra_dav/util.c:826: (apr_err=160004)
svn: PROPFIND request failed on '/wowace/trunk/!!!StandaloneLibraries'
subversion/libsvn_ra_dav/util.c:389: (apr_err=160004)
svn: Missing node-id in node-rev
Unable to get: !!!StandaloneLibraries

(This is with !!!StandaloneLibraries, but same for all addons today.)

Any information on how to rectify this would be nice. Thanks again.

Unfortunately the error messages indicate a problem with svn.wowace.com and not the script itself. There is nothing I can do to fix this, the only thing is to wait till the SVN server is fixed.

I had a feeling that's what it was, didn't know if they changed the url for trunk or what not, just figured I'd see if it was just me or not.

Is there any way to use this script to add addons with the libs still embedded?

Quote from Moong »

Is there any way to use this script to add addons with the libs still embedded?

Yes, but you will need to edit the .addonpkg.addons file in your stage directory, and add a line for each addon that needs externals. Something like:
replacing addonname with the name of the addon you wish to fetch with externals. You can also add a "-nosplit" to prevent an addon from being split into modules.

Okay, just go ahead and call me an idiot, but where do you actually get the perl script? I looked for an archives area but could never find it. Please help.

Thanks,
OneTrueBob

Nevermind... found it. I am an idiot.

addonpkg is now available from my google code page

Quote from onetruebob74 »

Okay, just go ahead and call me an idiot

You're an idiot.

The reason why is not known to me at this time, it's probably your fault.

I have nothing constructive to add.

PS: not really. kisses!

There is a beta at my svn http://nayala-wow.googlecode.com/svn/trunk/addonpkg/ that adds a undocumented option "-mac_mp3_workaround". This option causes mp3 filenames to get mangled when addons are installed to prevent the PlaySound bug. I haven't released the new version yet because there are a few new features that I'm still working on. (I.e. The tar bundle at the site is from an older stable version.)

You can also use addonpkg to install a non-svn addon and mask mp3 files until this bug is fixed using something like.

addonpkg -install -mac_mp3_workaround path/DownloadedAddon.zip

Brief summary of the other changes (note this stuff is still in flux):

• Stage directory is now organized into subdirectories. For example all wowace addons will go under wowace, auctioneer addons under actioneeraddons. You can edit the .addonpkg.addons file to change where addons are played. Just add an -override flag and change the subdir how you wish. You can operate all addons in a subdirectory just by listening that directory name in the list of addons. For example "addonpkg -fetch -revision '<#####' wowace" might be useful to update to revision ##### of addons hosted at wowace.
• TOC files are editted when installed to comment out embeds.xml, modules.xml and files that are not present.
• TOC files now include information which addon a module came from if it was split using the X-addonpkg-parent tag.
• TOC files installed by addonpkg have the X-Package-Manager tag with the value "addonpkg"
• .svn directories are no longer copied when installing with addonpkg.
• Aliases can refer to multiple addons, for example AuctioneerAdvancedSuite.
• Additional dependencies for the -libs option can be harded coded into the addon database. For example: "addonpkg -fetch -libs LightHeaded" gets all the LightHeaded_*_Data addons even though they are not mentioned in the LightHeaded.toc
• I've fixed some handling of filename case issues.

Edit: These changes were included in version 2007-10-15

Version 2007-10-16 updates the default database to the new SVN for the Auctioneer addons.

Version 2007-10-19 is now available. New feature organize your addons into groups. http://code.google.com/p/nayala-wow/downloads/list

For example:
addonpkg -setgroup raid_addons BigWigs oRA2 Omen ...
addonpkg -setgroup solo_addons AuctioneerAdvancedSuite ...

Switch to raid mode:
addonpkg -install raid_addons
addonpkg -uninstall solo_addons

Switch to solo mode:
addonpkg -install solo_addons
addonpkg -uninstall raid_addons

This is also useful for testing compatibly with mutually exclusive groups of addons.

Note set group is additive, so you can do
addonpkg -setgroup groupname A C
addonpkg -setgroup groupname B C D
And A B C D will all be part of the group groupname.

Version 2007-11-13 is now available. New feature enable and disable addons, work with individual modules in addons that split into multiple modules when installed. Aliases as also now available from the command line instead of just the database file. Aliases and groups are very similar in purpose. http://code.google.com/p/nayala-wow/downloads/list

The difference between aliases and groups is that an addon can only be in one group, while addons may be in multiple aliases. When refering to a group by name it only considers the addons in the group that have been previously fetched. Aliases always consider all the addons in the alias. The -setalias command is used to assign addons to aliases.

To enable an addon use the -enable command, for example:

addonpkg -enable -libs MyAddon

would enable MyAddon and all the libraries it uses for all characters you have in WoW.

Disabling is done with the -disable command, for example:

addonpkg -disable MyAddon

Disables MyAddon. Notice I did not use the -libs in this example since that could possibly disable all the addons.

Another example, let's suppose that you are getting ready to update your addons in bulk and are worried that something might break.

addonpkg -stage-dir "%INSTALL%" -archive ~/Desktop/myaddons.zip -all

Save a copy of your current addons incase you need to restore them.

addonpkg -fetch -all

Update all your addons.

addonpkg -outdated

Figure out which addons changed

addonpkg -install -all

Install everything. Log in to wow... Yikes you are getting a bunch of errors... Log out.

addonpkg -disable -all

Disable all your addons.

cd /Applications/World\ of\ Warcraft/Interface/StageArea
addonpkg -enable -libs a*

Enable all the addons beginning with the letter a and their libraries.
Log back into wow, hmm stuff is working. Repeat with b* etc... until you figure out which addon is giving you trouble.
If you don't feel like checking you can always restore your archive with:

addonpkg -enable -all
addonpkg -install ~/Desktop/myaddons.zip

Edit: I'm working on a version that uses the RSS feed to avoid fetching addons that have not changed. It's not been packaged up yet but is in revision 87 of my svn at http://nayala-wow.googlecode.com/svn/trunk/addonpkg/ Now available as 2007-11-26 release. This should speed up downloads and reduce load of the SVN servers, let me know if you have any issues with it.

Version 2007-12-19 is now available. It should offer similar speed ups for fetching addons from other SVNs as the previous version did for fetching from wowace's. Other than that there is no reason to upgrade.