Aliasing imports. about glock HOT 4 CLOSED

Forks for me always divide into two situations:

• Long-lived forks, where I may open pull requests to the upstream repo, but they won't merge or are slow to merge pull requests.
• Short-lived forks, which exist just to send a particular pull request.

For long-lived forks, I think that changing the GLOCKFILE and rewriting your imports to use it is appropriate.

For short-lived forks, I add my fork as a remote to the primary repo location (so that I don't have to rewrite imports to have my code use the change locally), and when the main repo merges the change, then I update the GLOCKFILE so that others on the team get the change.

This article describes that flow pretty well
http://blog.campoy.cat/2014/03/github-and-go-forking-pull-requests-and.html

Does that address your use case?

Thanks for using Glock!

from glock.

This makes sense, and I've pretty much been using the short-lived forks approach for most things. However I don't always know from the outset if I'll have a long or short lived forks, and inevitably I'll have to share the build dependencies with other team members before this.

Even for medium/long-lived forks, rewriting imports can be a challenge. I have a patch for revel that brings a-feature-I-really-need-right-now-but-isnt-on-the-roadmap-until-next-release-or-the-release-after-that, and for a library like revel changing all the import statements is a non-trivial task (and affects many of the tools used), especially since I really would like to get up to date once said feature is out.

I've only seen a few of dependency managers (https://github.com/mattn/gom, https://github.com/vube/depman, https://github.com/nitrous-io/goop) that support some kind of workaround for these situations, but they have other deficiencies that kept me from going with them.

from glock.

It seems like it would be complicated for Glock to support that use case. (The ability to specify a destination directory different from the natural location)

It sounds like a large part of the difficulty you have is the rewriting-imports step. Maybe addressing that would be the easiest thing? I believe that there are dedicated programs for that, but doesn't a simple find-replace of the full import paths

from glock.

For something like revel, it's not just import paths, but template paths, modules etc...
I have a work around for now, but will seek some permanent solution. It could be something as simple as manually specifying the clone command... but granted, perhaps not your itch at the moment.

from glock.