I am used to using the .pkgmeta file for a single folder mod. I am currently creating a ZIP file for GnomeSequencer-Enhanced and pushing it Curse the old fashioned way but want to do something a bit more refined.
You should have LibStub, CallbackHandler-1.0, and all the Ace3 components listed in GS-Core; then you reference them in each module's ToC just as you would for any other AddOn.
Putting multiple references in the .pkgmeta is pointless.
You can also use move-folders in the .pkgmeta to make GS-SequenceEditor its own AddOn.
The only way to get multi-folder addons to package the way you want is using the move-folders pkgmeta option which moves sub-folders to the root after packaging.
If you would package your addon without move-folders, all would be inside a "GnomeSequencer-Enhanced" folder and nothing would get loaded.
There is several approaches to setting up move-folders, either how KuiNameplates does it by moving everything, or having the "core" in the top level folder and only moving the "plugin" to the root, which is what some other addons do.
Here's an example of having the core files at top-level and moving "plugin" folders with the packager, that works both as-is (for you during development) and after packaging (for users):
The TOC and .pkgmeta files will be of most interest; the "Config" folder gets moved to "oUF_Phanx_Config" up at the same level as the main "oUF_Phanx" folder. In an un-packaged copy (eg. your working copy) the Config/* files get loaded from the main addon's TOC, wrapped in @do-not-package@ keywords so the packager removes those lines.
I'm prob still doing some things the hard way in that while the three know about each other i havent figured out how to make them a seamless object. The duplication works for me though in that some people only use the GS-Core and dump the rest. They then have just what they need to just run that.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI am used to using the .pkgmeta file for a single folder mod. I am currently creating a ZIP file for GnomeSequencer-Enhanced and pushing it Curse the old fashioned way but want to do something a bit more refined.
My Github repository is located at : https://github.com/TimothyLuke/GnomeSequenced-Enhanced/
This is my first cut of a .pkgmeta file would this be correct? At the end of the day I only want the three folders present within the ZIP at the root.
package-as: GnomeSequencer-Enhanced externals: GS-Core/lib/LibStub: url: svn://svn.wowace.com/wow/libstub/mainline/trunk tag: latest GS-Core/lib/AceLocale-3.0: url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceLocale-3.0 tag: latest GS-SequenceEditor/lib/LibStub: url: svn://svn.wowace.com/wow/libstub/mainline/trunk tag: latest GS-SequenceEditor/lib/CallbackHandler-1.0: url: svn://svn.wowace.com/wow/callbackhandler/mainline/trunk/CallbackHandler-1.0 tag: latest GS-SequenceEditor/lib/AceAddon-3.0: url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceAddon-3.0 tag: latest GS-SequenceEditor/lib/AceLocale-3.0: url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceLocale-3.0 tag: latest GS-SequenceEditor/lib/AceConfig-3.0: url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceConfig-3.0 tag: latest GS-SequenceEditor/lib/AceConsole-3.0: url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceConsole-3.0 tag: latest GS-SequenceEditor/lib/AceEvent-3.0: url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceEvent-3.0 tag: latest GS-SequenceEditor/lib/AceGUI-3.0: url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceGUI-3.0 tag: latest ignore: - GS-MyMacros - GS-HighPerformanceMacros - .travis.yml - README.md - spec-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorPutting multiple references in the .pkgmeta is pointless.
You can also use move-folders in the .pkgmeta to make GS-SequenceEditor its own AddOn.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorHere is an example with a similar setup:
https://github.com/kesava-wow/kuinameplates2/blob/master/.pkgmeta
If you would package your addon without move-folders, all would be inside a "GnomeSequencer-Enhanced" folder and nothing would get loaded.
There is several approaches to setting up move-folders, either how KuiNameplates does it by moving everything, or having the "core" in the top level folder and only moving the "plugin" to the root, which is what some other addons do.
https://github.com/Phanx/oUF_Phanx
The TOC and .pkgmeta files will be of most interest; the "Config" folder gets moved to "oUF_Phanx_Config" up at the same level as the main "oUF_Phanx" folder. In an un-packaged copy (eg. your working copy) the Config/* files get loaded from the main addon's TOC, wrapped in @do-not-package@ keywords so the packager removes those lines.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI'm prob still doing some things the hard way in that while the three know about each other i havent figured out how to make them a seamless object. The duplication works for me though in that some people only use the GS-Core and dump the rest. They then have just what they need to just run that.