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.
The latest version fixed the problem with SpecialEvents.
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 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
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?
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.
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.
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
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.
Save a copy of your current addons incase you need to restore them.
addonpkg -fetch -all
Update all your addons.
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:
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.