• 0

    posted a message on Standalone packager for your Git project
    Quote from Phanx
    1. Support for the "move-folders" directive would be nice, and shouldn't be too hard to implement.


    I was reading the wiki and trying to determine exactly how "move-folders" works. Does it actually move the directory from the specified path to the top-level with the specified name? Or does it just copy the directory?
    Posted in: General Chat
  • 0

    posted a message on Grid — compact party/raid unit frames
    When I have problems making the aura show after adding it to Grid, almost every time it is due to the aura name not being entered properly. It has to exactly match the name of the buff in the tooltip. When I go to fr.wowhead.com, it says the name of the buff is "Clarté d’esprit", so could you please try that instead?
    Posted in: Grid & Grid2
  • 0

    posted a message on ANNOUNCEMENT: Grid is moving from SVN to Git
    username: jlam
    email: [email]jlam88@gmail.com[/email]
    Posted in: Grid & Grid2
  • 0

    posted a message on Standalone packager for your Git project
    I've now created a GitHub repository for the release script and cherry-picked the history for the project. It's available as curseforge-packager.
    Posted in: General Chat
  • 0

    posted a message on Standalone packager for your Git project
    One last use case for this script: I hack on my addons outside of my live addon directory, but I do this to publish my changes directly into the live addon directory:
    sh release.sh -eoz -r "/c/Programs/World of Warcraft/Interface/AddOns"

    This skips fetching externals and creating the zip file, but otherwise stages all of the files in your checkout and creates the changelog into the live addon directory. The funny path to the AddOns directory is just how the bash shell included with the Windows Git distribution wants paths -- UNIX-style instead of DOS-style.

    This staging allows me to be fairly certain I'm running the exact same code as if I had installed the addon from Curse Client, so I know what users are going to be seeing.
    Posted in: General Chat
  • 0

    posted a message on Standalone packager for your Git project
    Quote from Phanx
    Looks very promising. I'll be sure to give it a try the next time the packager is ignoring me. My only comments for now are that:

    1. Support for the "move-folders" directive would be nice, and shouldn't be too hard to implement.

    2. It should probably also allow a "-beta" suffix:


    Yes, "move-folders" should be easy based on the description, but I don't use it so I've not touched it.

    Regarding "-beta", the way that release.sh currently works, all the stuff with tags is used mostly for assigning the version number and making the changelog. The assumption is that you want all changes since the previous release tag to the HEAD. If you don't tag the head, then it generates a Git-based version number that's basically the number of commits since the previous release tag. If you tag the head, then it uses the tag as the version number. Examples:

    1. HEAD is tagged "1.2.3" and previous tag is "1.2.2". Then the version number is 1.2.3 and changes are from 1.2.2 to 1.2.3.
    2. HEAD is tagged "1.2.3-beta" and the previous tag is "1.2.2". Then the version number is 1.2.3-beta and the changes are from 1.2.2 to 1.2.3-beta.
    3. HEAD is tagged "1.2.3-beta2" and the previous tags are 1.2.3-beta and 1.2.2. Then the version number is 1.2.3-beta2 and the changes are from 1.2.2 to 1.2.3-beta2.
    4. HEAD is untagged and 7 commits ahead of the previous tag 1.2.2. Then the version number is 1.2.2-7-g7e4ab1 (or whatever the hash for the HEAD is) and the changes are from 1.2.2 to HEAD.
    Posted in: General Chat
  • 0

    posted a message on Standalone packager for your Git project
    Feel free to take it and dump it in a repo to hack on it. I consider it public domain.
    Posted in: General Chat
  • 0

    posted a message on Standalone packager for your Git project
    I'm just posting this here in case there's interest. I was having a lot of trouble with the WowAce packager that was hooked into the Ovale Git repository, so I decided to write my own packager for Ovale. When I've pushed all my changes, I just run this script and it reads my .pkgmeta and .toc files and generates an appropriate ZIP file and embeds a CHANGELOG.txt file with the commits since the previous release. All you need is a Windows Git installation, and you should have all the base tools used by this script. If you have SVN externals, you'll also need a Windows SVN client installed to fetch them. If you have 7-Zip installed, it will create the ZIP file. It's assumed that all of these things can be executed from the command line.

    You can find it over on GitHub:
    # release.sh generates a zippable addon directory from a Git checkout.
    #
    # release.sh works by creating a new project directory, checking out external
    # repositories within the project directory, then copying files from the Git
    # checkout into the project directory. The project directory is then zipped to
    # create a distributable addon zipfile.
    #
    # release.sh reads .pkgmeta and supports the following directives:
    # - externals
    # - ignore
    # - manual-changelog
    # - package-as
    #
    # release.sh supports the following repository substitution keywords when
    # copying the files from the Git checkout into the project directory.
    # - @project-version@
    #
    # release.sh reads the TOC file, if present, to determine the name of the
    # project.
    #
    # release.sh assumes that annotated tags are named for the version numbers for
    # the project. It will identify if the HEAD is tagged and use that as the
    # current version number. It will search back through parent commits for the
    # previous annotated tag that is a release version number and generate a
    # changelog containing the commits since that previous release tag.
    #
    # By default, release.sh creates releases in a "release" subdirectory of the
    # top-level directory of the Git checkout.
    Posted in: General Chat
  • 0

    posted a message on VBS & BAT files in repositories
    Is there a way to allow checking in a .vbs or .bat file into a repository? I write scripts to automate certain tasks in Windows that I use during development and I'd like to include them in the repository if possible. I understand the concern about distributing those and getting flagged by virus checkers, but couldn't the packager just ignore those files when creating the ZIP file?

    Currently, I work around this by writing shell and perl scripts that have no restrictions on being pushed to the CF repository, but sometimes you just have to have a VBS script to do the job.
    Posted in: General Chat
  • 0

    posted a message on Packager issues
    I could really use some help with getting the packager to correctly package Ovale again if there's anyone that can look into it.
    Posted in: General Chat
  • 0

    posted a message on Packager issues
    I guess I can "work around" this by tagging and pushing 250 betas until the packager catches up to the correct release tag. Just let me know if I should go this route.
    Posted in: General Chat
  • 0

    posted a message on Packager issues
    I did exactly this. The packager now incrementally thinks the latest release is 3.1.16, 3.1.17, 3.1.18, etc., every time I make and push a new tag. I don't really see how this has anything to do with Git, but I guess that's just me.
    Posted in: General Chat
  • 0

    posted a message on Packager issues
    I'm 100% sure I just blew up the packager by accidentally pushing all of my tags in my Ovale repository instead of just the latest one. I have no idea how to fix this.

    Currently, Curse.com believes the latest tag is 3.1.15 when it should be 6.0.38.
    Posted in: General Chat
  • 0

    posted a message on Grid — compact party/raid unit frames
    Quote from carcanathor
    I've been using Grid2+clique for a very long time.

    This is the thread for Grid, not Grid2.
    Posted in: Grid & Grid2
  • 0

    posted a message on Packager packing from GitHub?
    Quote from Phanx
    Fortunately, if you're using GitHub, that means you're using Git, and that means you can just create a Git repo for your addon on CurseForge, add it as a second remote, and push to all remotes instead of just GitHub. In fact, if you set that up and push your current repo to it, the packager should make packages for each of the tags you've already created.


    For what it's worth, this is exactly what I do with my projects -- using both GitHub and CurseForge/WowAce as remotes for my Git projects. It works just fine and allows WowAce to do the packaging while you have access to all of the nice tools over at GitHub for browsing and merging. You just have to be careful with pushing tags to WowAce since it'll treat your most recently pushed tag as your latest release.
    Posted in: General Chat
  • To post a comment, please or register a new account.