[Canonical-tech] Handling active dependencies in Go

[Kapil Thangavelu]

On Tue, Jan 8, 2013 at 7:01 AM, Jonathan Lange <jml at canonical.com> wrote:

> On 8 January 2013 12:58, John Arbash Meinel <john.meinel at canonical.com>
> wrote:
> ...
> > [1]  IIRC it does this by playing games with site.py configuration at
> > runtime, and using a custom 'py' script. It removes all default search
> > paths, and sets each path manually. One could imagine a build tool
> > that built up GOPATH based on explicit locations for versions of
> > dependencies.
> >
>
> Correct.
>
> If you squint hard enough, buildout as Launchpad uses it is a way of
> emulating static linking for Python.
>
> jml
>
>
to me the ideal way for this would be something like virtualenv for go.
where by GOPATH is set manually and a requirements.txt file could specify
vcs revisions against each pkg for use when fetching via go get or some
augmented version of the same. That avoids the need for lock step branching
and source modification for frozen release.

-k
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130108/8f56b4f3/attachment.html>