Evaluate Package Managers for Go about magistrala HOT 5 CLOSED

I have experimented with Glide. Nice tool.

However, Go seems to have this philosophy: http://stackoverflow.com/questions/24855081/how-do-i-import-a-specific-version-of-a-package-using-go-get

Adding new tools complicates the dev. KISS.

Mainflux imports only a handful of external packages, and all of them are well maintained. Our TDD tests should determine when things are broken. If ever something is broken, then we might consider what to do with this particular package and/or use Glide to lock package versions.

I think however that this case will not come, and that we might relay on simple go get and latest GitHub package braches (which by mentioned philosophy should be stable).

I will close the issue for now.

from magistrala.

@janko-isidorovic and @manuio run into the issue of Iris new version incompatibility with current Mainflux API.

Now number of dependencies is significant and we must lock the their versions.

Glide must be integrated in our project.

Look at Hydra for example of integration (https://github.com/ory-am/hydra#building-from-source)

from magistrala.

@mijicd @nmarcetic I see that this project: https://github.com/brocaar/loraserver for examples uploads in GitHub all the vendor packages - i.e. code. This is opposite to npm philosophy, but can be useful for end-user, so he do not care if some GitHub package does not exist anymore.

What is your opinion on this?

from magistrala.

I've added Glide, but would you consider maybe govendor - do you think it i s simpler to have than Glide?

from magistrala.

Finally, Glide it is.

Closing this one.

from magistrala.