Big +1 to getting our client release process nailed down! That'll be huge in
terms of managing those dependencies. :-)
- Gabriel
> -----Original Message-----
> From: openstack-bounces+gabriel.hurley=nebula....@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel.hurley=nebula....@lists.launchpad.net] On Behalf Of
> Monty Taylor
> Sent: Wednesday, June 13, 2012 8:28 AM
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] [Swift] swift.common.client and swift CLI has
> moved to its own project python-swiftclient
>
>
>
> On 06/13/2012 10:58 AM, Juan J. Martinez wrote:
> > On 13/06/12 15:42, Dan Prince wrote:
> >> Okay. It looks like Swift also still depends on swiftclient. Long term it
> would be nice if we could build and unit test swift without relying on the
> swiftclient package. Could we:
> >>
> >
> > I can't see the reason for that, swiftlclient is a dependency of swift
> > (as webob, greenlet, pastedeploy, etc).
>
> I agree. At the moment it's slightly more ugly because we haven't finalized
> the pypi release process for our client libs... but we should have that in the
> next week or so, and then it should be perfectly possible to treat it just
> like
> anything else.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
