The juju/go trunk has moved!

[Gustavo Niemeyer]

The thinking was to have the bottom package as "juju" being a useful
package. This scheme also enables having juju2, etc once we want to
stabilize the API itself. That said, it's easy to change now and I'm not
rooted on those ideas either. Let's talk next week and agree on something.

gustavo @ http://niemeyer.net
On Jun 7, 2012 9:58 AM, "roger peppe" <roger.peppe at canonical.com> wrote:

> On 7 June 2012 12:36, Kapil Thangavelu <kapil.thangavelu at canonical.com>
> wrote:
> >
> >
> > On Thu, Jun 7, 2012 at 5:03 AM, roger peppe <roger.peppe at canonical.com>
> > wrote:
> >>
> >> On 6 June 2012 20:43, Gustavo Niemeyer <gustavo.niemeyer at canonical.com>
> >> wrote:
> >> > As previously mentioned, we've been moving the Go development
> >> > activities to a new project in Launchpad:
> >> >
> >> >    https://launchpad.net/juju-core
> >> >
> >> > As arranged over the whole day on IRC, the trunk for the Go port is
> >> > now at a new location:
> >> >
> >> >    launchpad.net/juju-core/juju
> >>
> >> Sorry, I wasn't there for the discussion, but could you briefly
> >> say why the import paths are "launchpad.net/juju-core/juju/foo" rather
> >> than "launchpad.net/juju-core/foo" ?
> >>
> >> The extra "juju" seems unnecessary (and other projects such
> >> as goamz and gozk don't have them)
> >>
> >> One other thing: i tried "bzr branch launchpad.net/juju-core/trunk"
> >> and got this error:
> >>
> >> bzr: ERROR: Permission denied: "Cannot create 'trunk'. Only Bazaar
> >> branches are allowed."
> >>
> >> Is this all because we don't want to define the Go port as "trunk" in
> >> juju-core?
> >>
> >
> > bzr branch lp:juju-core
> >
> > for an existing branch
>
> N.B. this doesn't work when bzr is aliased to cobzr, although
>
>  cobzr branch lp:juju-core/juju
>
> does.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20120607/b74da467/attachment.html>