Packaging about ngrok HOT 16 CLOSED

There are! But since I don't have an OS X machine available to develop a brew recipe on, it kinda depends on community involvement. Would love to have your help getting that together. Here's the thread discussing it.

Homebrew/legacy-homebrew#20839

from ngrok.

Packaged for NixOS: NixOS/nixpkgs@78876a8

from ngrok.

Just a note that I've submitted Homebrew/legacy-homebrew#23732. Really straightforward to build (thank you!) so maintenance should be pretty easy as well.

from ngrok.

@nebhale Thank you! Hopefully we can figure out how to get it "bottled" as well. I'll ask them on the thread.

from ngrok.

Not sure that you really need it to be bottled since it builds in a couple of seconds. But maybe they have a better idea of what candidates for bottling are.

from ngrok.

It will only build in seconds if you already have hg, bzr and golang installed. Installing those dependencies, especially golang, can up to a few minutes depending on your machine. I've asked them about it.

from ngrok.

I read that ngrok updates itself when run. Does this play nice with packaged installs? Is it possible to disable auto-updating when compiling ngrok? I'd like to see ngrok in MacPorts.

from ngrok.

@breun You can disable it when compiling ngrok, although I would greatly appreciate it if you didn't. ngrok gives users the control to disable auto-updating if they don't want it.

from ngrok.

@inconshreveable When software is installed by a package manager it would create a pretty confusing situation if a user installed version X of ngrok, ngrok updated itself to version X+1, but the package manager still reported version X being installed.

By the way a binary installed through MacPorts would also be owned by root, so not able to update itself when run by a normal user.

from ngrok.

@breun Yep, I understand. And it wouldn't be able to update itself . . . unless they run it as root, in which case the bet is off. If you want a non-updating version, I'd highly suggest compiling it in that fashion. I think you can use the go build tag !autoupdate to disable it, but I'll have to check. You can see how the Makefile sets it for the release tag.

from ngrok.

I've installed Go 1.2.1 and Mercurial 2.9.1 via MacPorts and make executes successfully.

I'm not too familiar with either Go or Makefiles, but I see that src/ngrok/client/update_debug.go contains // +build !release,!autoupdate and an autoUpdate function that does nothing.

How does one make ngrok with this !autoupdate build tag?

from ngrok.

I had a go a creating an ngrok Portfile for MacPorts: https://trac.macports.org/ticket/43077 I'm having some trouble though. I've dealt with the lack of an install goal in the Makefile (just have the Portfile copy the files), but the fact that the build phase is downloading dependencies is apparently problematic (or so someone told me old the #MacPorts IRC channel). MacPorts has a fetch phase and a patch is probably required to make this work. This is my first Portfile though, so I'm not that experienced yet.

And I still don't know how to build ngrok with auto-update disabled. What would be the exact make command for that?

from ngrok.

@breun Sorry for the slow reply. The truth is that the Makefile isn't really set up for that at the moment. Here's what you can do to get a non-updating build though:

make clean
make client-assets BUILDTAGS=release
GOPATH=`pwd` go install -gcflags "-N -l" -tags 'release !autoupdate' ngrok/main/ngrok

This is pretty horribly kludgy. I'd be happy to have a makefile that's more flexible and allows different options to be turned on/off. I'm not sure if the "right way" to do this is to bite the bullet and learn autotools or if we can just make the Makefile more clever and still support all of the different build options that are required.

from ngrok.

Seems to be in Homebrew now. Is this not an officially supported package?

from ngrok.

@kevinSuttle i'm not sure what you mean, but the homebrew package is built from this ngrok source tree. this particular issue is honestly too broad. I'm going to close it. It would be nice to package ngrok as .app and .msi for osx/windows, but if anyone wants that, we'll make separate issues for each one and any other change to the building/packaging of it.

from ngrok.

@inconshreveable Thanks for the explanation.

from ngrok.