• 0

    posted a message on [pkgmeta] Solved - Libraries not being bundled

    Ideally, I didn't want to add the libraries manually if I work on this across multiple computers which is why I wanted my repository to include the Libs folder. But this just seems easier way to deal with it :)

    Thanks Tuhlijin for the suggestion, I added the Libs folder to my .gitignore and removed the ignore in my .pkgmeta. Everything works now!

    Posted in: AddOn HELP!
  • 0

    posted a message on [pkgmeta] Solved - Libraries not being bundled

    Solution

    @Torhal pointed out I was adding the same folder I was pulling the libraries into as my ignore folder.

    externals:
        Libs/AceAddon-3.0:
            url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceAddon-3.0
            tag: latest<br />ignore: - Libs

    This use to work for me but seems like something has changed. A solution suggested by @Tuhljn was to ignore the Libs folder using my source control Ex: .gitignore. instead of the .pkgmeta.


    Hello, I have been trying to get the Automatic packager to include libraries with my addon. It appears my old [2 week old] .pkgmeta file does not work with my other addon.

     

    Here is the pkgmeta file below, the zip file is created however the no-lib and "lib" version are exactly the same with no Libs folder even created.

    package-as: BaikItemLevel
    
    externals:
        Libs/AceAddon-3.0:
            url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceAddon-3.0
            tag: latest
        Libs/AceConfig-3.0:
            url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceConfig-3.0
            tag: latest
        Libs/AceConsole-3.0:
            url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceConsole-3.0
            tag: latest
        Libs/AceDB-3.0:
            url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceDB-3.0
            tag: latest
        Libs/AceDBOptions-3.0:
            url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceDBOptions-3.0
            tag: latest
        Libs/AceHook-3.0:
            url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceHook-3.0
            tag: latest
        Libs/AceGUI-3.0:
            url: svn://svn.wowace.com/wow/ace3/mainline/trunk/AceGUI-3.0
            tag: latest
        Libs/CallbackHandler-1.0:
            url: svn://svn.wowace.com/wow/callbackhandler/mainline/trunk/CallbackHandler-1.0
            tag: latest
        Libs/LibStub:
            url: svn://svn.wowace.com/wow/libstub/mainline/trunk
            tag: latest
    
    ignore:
        - Libs
    
    I even copied parts of the tutorial and still don't get the libraries packaged with my app.
    
    package-as: BaikItemLevel
    
    externals:
        libs/LibStub:
            url: svn://svn.wowace.com/wow/libstub/mainline/trunk
            tag: latest
        libs/CallbackHandler-1.0:
            url: svn://svn.wowace.com/wow/callbackhandler/mainline/trunk/CallbackHandler-1.0
            tag: latest
    
    ignore:
        - Libs # ignore the scripts folder
    
    Posted in: AddOn HELP!
  • 0

    posted a message on Unable to update project + missing libraries [Solved - User error]

    Ahh okay, did not know about this dashboard, this is something I can work with. Thank you!

    Ya the quotes were a desperate attempt in getting something working. 

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Unable to update project + missing libraries [Solved - User error]

    Solved

    Looks like I am having issues with the .pkgmeta file when updating the SVN format to the new https url. As @Torhal pointed out, check Dashboard->Builds->#<build_number> to see what went wrong with your builds


    Hello, I am having issues with pushing new updates to cursed and getting any external libraries with my new addon. 

    Addon link

     

    I followed similar methods with my previous addon BaikActionbar and everything worked there. Maybe theres some conflicts with the new curseforge site?

    New Releases With Tags:


    I seems to have trouble updating with tags. It seemed to do the initial alpha commit. I was unable to get a beta tag to work, but any subsequent tags didn't. It almost as if I can only submit one target per release "type" (alpha, beta, maybe release?).

     

    The commands I use on git to push to the cursed servers:

    git tag 1.0-beta
    git push wowace 1.0-beta

    Note: wowace being my remote for the cursed repository since I have the origin at bitbucket.

    This usually works for me, not sure if I am messing something up. I even update the master and I get zero errors. When I try to repush, I just get a message indicating that everything is up-to-date. Checking the .git/config file, my remote alias is pointing to the correct url. So not sure if I am messing up or if this is a known issue :/

     

    Edit: I should clarify in the settings on the website, I set it to package all commits. I put my files in the archive to try and prevent people from downloading anything.

     

    Exported Libraries:


    I was not getting any external libraries to be packaged with my addon. I have done it before with the "older" version that worked a few weeks back. Again, followed similar format to my previous addon, noticed that there has been some updates. I tried changing it to pkgmeta.yaml. Updated all the libraries to use the https git link instead of the old svn link. Not completely sure if this is fixed since the above issue isn't fixed.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Packager not packaging my tags?

    I am running into similar issues as well. I add git-tags and they don't seem to updating on the site when I push them. I tried switching to something else such as alpha->beta and was able to see it go on the website. But if I don't see any further changes.

    Posted in: AddOn HELP!
  • To post a comment, please or register a new account.