After speaking to Torhal (who the project claims to be the manager of this Babble lib), i added DigSites into my babble update script, which will export the babble locales directly into the repository.
Touching the toc would not update translations anyway, its no longer using the packagers localization tag, my scripts export the translation into the repository directly.
This allows people that don't use the wowace packager to directly use the svn versions, which was the main argument we made back then to do it this way.
Like i said, if you for some reason need an updated package, instead of poking the toc, just send me a message.
Someone sent me a PM with a partial list of the dig site blobIDs, mostly for Pandaria. Great, I know about ArcheologyGetVisibleBlobID and ArcheologyMapUpdateAll, but neither gives you a comprehensive list of all dig sites, nor does it convert the IDs into locale independent names. That is why I never used the APIs. Of course, somehow, Blizzard can put that information on the map, so I'm wondering how they do it?
Yes, I am trying to find a way to depreciate this library.
Tagging a TOC bump for a library doesn't seem like a thread-bump-worthy issue... anyone using standalone libraries should be savvy enough to know how to use the "Load out of date addons" checkbox. If you have tagging permissions on the project, and you think it needs a tag and is in a release-ready state, just tag it. :/