Originally Posted by Tutje
callbackhandler file in your addon dir.?
|
much a cosmetic thing, you dont have to put it iin the dir since this is the lib author providing it
Originally Posted by Tutje
When there is a update you need to replace the xml file as well.
|
No because usually any mod author uses the SVN where he stores first its mod online, (See TortoiseSVN tuts and the SVN options to familiarize you with it), so he do not have to upload the libraries in the SVN but libraries are set externals with the property svn:externals so for exemple in my project easydnd (the beta 45 not stable r33) the svn folders has this externals
Code:
libs/AceAddon-3.0 svn://svn.wowace.com/wow/ace3/mainline/trunk/AceAddon-3.0/
libs/AceGUI-3.0 svn://svn.wowace.com/wow/ace3/mainline/trunk/AceGUI-3.0/
libs/AceConfig-3.0 svn://svn.wowace.com/wow/ace3/mainline/trunk/AceConfig-3.0/
libs/AceConsole-3.0 svn://svn.wowace.com/wow/ace3/mainline/trunk/AceConsole-3.0/
libs/AceDB-3.0 svn://svn.wowace.com/wow/ace3/mainline/trunk/AceDB-3.0/
libs/AceDBOptions-3.0 svn://svn.wowace.com/wow/ace3/mainline/trunk/AceDBOptions-3.0/
libs/AceEvent-3.0 svn://svn.wowace.com/wow/ace3/mainline/trunk/AceEvent-3.0
libs/AceLocale-3.0 svn://svn.wowace.com/wow/ace3/mainline/trunk/AceLocale-3.0/
libs/CallbackHandler-1.0 svn://svn.wowace.com/wow/ace3/mainline/trunk/CallbackHandler-1.0/
libs/LibStub svn://svn.wowace.com/wow/ace3/mainline/trunk/LibStub/
libs/Dewdrop-2.0 svn://svn.wowace.com/wow/dewdroplib/mainline/trunk/Dewdrop-2.0/
libs/LibDBIcon-1.0 svn://svn.wowace.com/wow/libdbicon-1-0/mainline/trunk/LibDBIcon-1.0/
libs/Dewdrop-2.0/AceLibrary svn://svn.wowace.com/wow/ace2/mainline/trunk/AceLibrary/
This means anytime I will download a copy of my mods through TortoiseSVN it will automatically download for me the defined libs because they are externals and not managed by me , so when a new lib is released I don't have to care on updating it, TortoiseSVN does it!
The good side with wowinterface is that you also have a webinterface
http://svn.wowinterface.com/svn.php to publish package directly from svn to your addon pages, so the zip will be generated with libs already included because wowinterface goes to download them for you because you had setup svn:externals links =)
Sounds huge at starts but thats really easy to understand, anything you include in your mod which is not coded by you is a library you should setup in svn:externals to not care then on dlding it on x site to upload on y svn.
There is just for now Git projects to force in your mod like LibDataBroker doesnt use svn but git and so on you cannot put a git link in your svn interface so better to upload directly only such mods in yours, but stuff like Callbackhandler are from Ace3 and directly available there svn://svn.wowace.com/wow/ace3/mainline/trunk/ for easy embedding