muesli / beehive-vendor Goto Github PK

Hi,

First of all, thanks for the nice project!

I'd like to create a Bee, but the packaging process is currently pretty broken.

What's the point of using a package manager, and committing vendor to git, when the strategy is

• Have dependencies in a separate repo, loaded as a submodule
• Not to commit the Gopkg.lock
• Delete and replace the whole vendor/ dir

Are there any reasons I'm missing for this non-idiomatic approach?

To the point of being broken: the github.com/jteeuwen/go-pkg-rss is not on GitHub anymore. This means that simply running dep init fails, as that dependency cannot be found.

I've seen you've forked the repo, so I guess the next thing to do is change imports in bee.

But before I open a PR for that, I'd like to propose that Bee moves to a more standard vendoring workflow:

• Committing the Gopkg.toml and Gopkg.lock files
• Just using dep ensure on the main repo
• Deleting this repo