Package Details: beehive 0.4.0-1

Git Clone URL: (read-only, click to copy)
Package Base: beehive
Description: A flexible event and agent system with lots of bees
Upstream URL:
Licenses: AGPL3
Submitter: derintendant
Maintainer: derintendant (muesli)
Last Packager: muesli
Votes: 2
Popularity: 0.000000
First Submitted: 2017-02-12 16:26 (UTC)
Last Updated: 2020-04-12 05:38 (UTC)

Latest Comments

muesli commented on 2019-05-31 13:39 (UTC)

@derintendant: No problem, and thank you for all the effort you already put into it. I just pushed the fixed PKGBUILD and bumped the version to 0.3.2. Let me know if this builds fine for you people!

derintendant commented on 2019-05-31 13:09 (UTC)

Hey @muesli, I have just added you! I really appreciate the help as I don't have that much experience with Go.

muesli commented on 2019-05-27 07:41 (UTC)

Hey @derintendant. Author of beehive here.

I think I got a working version of the PKGBUILD. We need to add '!makeflags'. We can also get rid of sym-linking beehive to GOPATH, as it can be build outside of it now.

I'd love to help out maintaining the package and push my changes. Could you add me?

fmartingr commented on 2019-05-19 13:26 (UTC)

@derintendant: Here it is

derintendant commented on 2019-05-19 12:33 (UTC)

Just fixed the error with go not resolving the needed dependencies.

@fmartingr: go-bindata should be automatically installed to the build-local GOPATH by the Makefile. Can you put the complete build output in a gist so I can take a look at it?

fmartingr commented on 2019-05-15 01:10 (UTC)

Build is not working for me with error: go-bindata: Command not found.

I'm assuming the go-bindata dependency is missing here? I've little to zero go knowledge.

derintendant commented on 2017-02-25 14:16 (UTC)

I have added the needed dependencies and everything seems in a working state now!

muesli commented on 2017-02-25 08:13 (UTC)

See the project's README: The beehive binary expects to find the config/ dir (a git-submodule) and assets/ dir in its current working dir.

derintendant commented on 2017-02-23 22:40 (UTC)

@ImNtReal: Curiously, I have not yet been able to fix that specific problem. I even encountered it when installing directly from source. To see that it also happens to you now, I suspect, that there might be some sort of compatibility problem with some Arch Package. I hope to take a look at this during the next few days.

ImNtReal commented on 2017-02-14 16:05 (UTC)

Is there a trick to getting more than a 404 when you go to http://localhost:8181?