Just a bugfix release:
* Removing .svn or .ignore from an addon wasn't picked up unless the addon folder was deleted for an update.
* Fix two exception problems in reload_data.
* Try to fix the UnicodeDecodeError (I couldn't replicate it, but I'm fairly sure I know what was causing it.
* Include Scoz's change to addon_versions.pkl.
I do have problems running wowace.py on Ubuntu Linux. WoW is installed in /home/thomas/.wine/drive_c/Programme/World of Warcraft and I tried to use --wowdir which does not work:I tried it with and without escaping, I edited wowace.py to hardcode the directory but nothing works. Any ideas?
I'm not sure what's causing that. I've tried setting up a parallel directory structure on my own machine, and this works:
Smarter TOC editing.
Use new "provides" data in the feeds to fill previously difficult dependencies.
'Accept-encodings: gzip' was missing from the last release. Ooops.
GUI version will load addons from server on launch instead of waiting for "check".
So glad I found this, as wau doesn't work for me at all.
I modified an addon a little, namely ag_unitframes. Is there any way to keep the script from updating that particular addon? How does the script know that an addon is an updatable ace2 addon?
Broadly speaking, it feels that an addon is a wowace addon if it has the same name as one on files.wowace.com. This could theoretically have a false-positive effect, of course, but I haven't seen it yet.
Edit: Ok, I found addon_can_be_updated in the code, but I neither understand the code nor the comment well enough... Do I have to create a folder or a file named .ignore in the addon directory? Should the filename be ".ignore" or "ignore"? Thanks.
Yup -- a file or folder named .ignore or .svn in the addon directory will make it never be updated.
With this new version I'm having a problems with Skinner. All the SkinMe entries seem to get commented out, probably because they don't exist and the user is expected to copy the ones they want from AddonSkins.
Also Prat/Pitbull and SpecialEvents-Loot are all telling me they cant find library instances.
Commenting gone too far? :P
I can give you a switch to toggle the commenting, I guess. I hadn't considered Skinner's weird structure.
Regarding the library instances, which libraries aren't being found? Of the addons you mentioned, I use PitBull, and haven't had any problems like that.
Currently in trunk is an option to run the various LOD scripts in addons. (Making this work on *nix involved having to make Python's zipfile module extract files with permissions intact, which is harder than you might think.)
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/os.py", line 166, in makedirs
OSError: [Errno 17] File exists: '/Applications/World of Warcraft/Interface/Addons/Ace2/AceLibrary'
I get this error a lot, and have to manually remove the offending directory before it'll install without crashing.
Interesting. I'm not sure why it's doing that -- it should be (a) deleting the entire directory first, and (b) checking to make sure the sub-directories don't already exist before extracting.
I'll have to investigate -- I haven't tried running this on a Mac yet.
Also if I install multiple addons, it attempts to install the dependencys for each, every time, no matter if they are already installed or not.
Looking at the snippet you provided, it's doing that because you're using -f. If you're forcing the update regardless of your installed version, that setting will flow-down to the dependencies, which will all get reinstalled anyway.
I've added a check to the SVN version to make sure it won't download a given addon more than once per update, though. I don't update with -f myself, so it hadn't occurred to me that it would behave like that.
Now checks to make sure an addon is still installed before downloading updates to it.
Warns when installing an addon with a required dependency that cannot be filled from the server. (This gets false positives sometimes if you're using unembedded libs -- it's very dependent on people putting the right folder names in the TOC.)
Warns if you'll need to restart WoW after updating an addon. (Checking to see if any file paths have changed.)
Unpackaging is really hooked up from the command line now, honest.
This release contains a gui. You don't have to use it. If you want to use it you'll need to have wxPython installed, then just run gui.py instead of wowace.py.
(The GUI has not been extensively tested, and is currently not as configurable as the command-line client. You have been warned.)