The first line is a valid directory which contains:
The second directory listed (/Library/Perl/5.8.1) doesn't exist. Any ideas?
edit: BTW if I do a locate Diff it isn't found (and my locate database is current).
edit: I installed Algorithm::Diff, then got an error for LWP. I installed LWP but am now getting an error for SVN:Client.pm. I have a feeling my version of perl is just not right or something... maybe because I'm running OS X 10.4 instead of 10.5?
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?
I tried updating my addons today using addonpkg but am getting svn errors for about half of my Ace addons. Example:
/usr/local/bin/svn update --ignore-externals /Applications/World of Warcraft/Interface/StageArea/Babble-2.2
svn: REPORT request failed on '/wowace/!svn/vcc/default'
svn: No such revision 24271
This probably has nothing to do with your script (I had installed the latest version before updating my addons) but does anyone know why I'm getting these errors? Like I said, it only affects some of my addons, so I have a feeling it's a problem with the files on the svn. I tried deleting the .svn file in the Babble-2.2 directory and using the -force option, but that didn't help.
The new features are really nice. I like especially like the -man option so's I don't have to check the forums each time I use it. ;)
I had a weird issue with the new script, though. It has OS 9 newlines (\015) rather than Unix newlines. I had to convert them to regular newlines before perl would interpret it. I didn't have this issue with the old script. Did you play with the new version in OS 9 before uploading it to the forums?