On 05/04/2016, Martin Packman wrote:
>
> Universe:
> juju-core (transitional depends juju-1.25)
> juju-1 (depends juju-1.25)
> juju-1.25 (/usr/lib/juju-1.25/bin/juju, wrapped as /usr/bin/juju-1)
> juju-local (depends juju-1.25, juju-mongodb, lxc bits)
> juju-local-kvm (depends juju-1.2
On 06/04/2016, Stuart Bishop wrote:
>
> How do our plugins know what version of juju is in play? Can they
> assume that the 'juju' binary found on the path is the juju that
> invoked the plugin, or is there some other way to tell using
> environment variables or such? Or will all the juju plugins
On 7 April 2016 at 16:46, roger peppe wrote:
> On 7 April 2016 at 10:17, Stuart Bishop wrote:
>> On 7 April 2016 at 16:03, roger peppe wrote:
>>> On 7 April 2016 at 09:38, Tim Penhey wrote:
We could probably set an environment variable for the plugin called
JUJU_BIN that is the juju t
On 7 April 2016 at 10:17, Stuart Bishop wrote:
> On 7 April 2016 at 16:03, roger peppe wrote:
>> On 7 April 2016 at 09:38, Tim Penhey wrote:
>>> We could probably set an environment variable for the plugin called
>>> JUJU_BIN that is the juju that invoked it.
>>>
>>> Wouldn't be too hard.
>>
>>
On 7 April 2016 at 16:03, roger peppe wrote:
> On 7 April 2016 at 09:38, Tim Penhey wrote:
>> We could probably set an environment variable for the plugin called
>> JUJU_BIN that is the juju that invoked it.
>>
>> Wouldn't be too hard.
>
> How does that stop old plugins failing because the new ju
On 7 April 2016 at 09:38, Tim Penhey wrote:
> We could probably set an environment variable for the plugin called
> JUJU_BIN that is the juju that invoked it.
>
> Wouldn't be too hard.
How does that stop old plugins failing because the new juju is trying
to use them?
An alternative possibility:
We could probably set an environment variable for the plugin called
JUJU_BIN that is the juju that invoked it.
Wouldn't be too hard.
Tim
On 07/04/16 17:25, Stuart Bishop wrote:
> On 7 April 2016 at 03:55, Marco Ceppi wrote:
>>
>> On Wed, Apr 6, 2016 at 10:07 AM Stuart Bishop
>> wrote:
>>>
>>>
On 7 April 2016 at 03:55, Marco Ceppi wrote:
>
> On Wed, Apr 6, 2016 at 10:07 AM Stuart Bishop
> wrote:
>>
>> On 5 April 2016 at 23:35, Martin Packman
>> wrote:
>>
>> > The challenge here is we want Juju 2.0 and all the new functionality
>> > to be the default on release, but not break our exist
On Wed, Apr 6, 2016 at 10:07 AM Stuart Bishop
wrote:
> On 5 April 2016 at 23:35, Martin Packman
> wrote:
>
> > The challenge here is we want Juju 2.0 and all the new functionality
> > to be the default on release, but not break our existing users who
> > have working Juju 1.X environments and no
On 5 April 2016 at 23:35, Martin Packman wrote:
> The challenge here is we want Juju 2.0 and all the new functionality
> to be the default on release, but not break our existing users who
> have working Juju 1.X environments and no deployment upgrade path yet.
> So, versions 1 and 2 have to be co
On Tue, Apr 5, 2016 at 1:37 PM Martin Packman
wrote:
> On 05/04/2016, Adam Collard wrote:
> > Will there be a transitional release of 1.25.x that also gives us a juju1
> > binary to facilitate this?
>
> Yes, the plan entails both an update to the juju in main for the 2.0
> release and a new juju
On 05/04/2016, Adam Collard wrote:
> Will there be a transitional release of 1.25.x that also gives us a juju1
> binary to facilitate this?
Yes, the plan entails both an update to the juju in main for the 2.0
release and a new juju 1.25 in universe that cooperates with the
changes.
For the debia
Will there be a transitional release of 1.25.x that also gives us a juju1
binary to facilitate this?
On Tue, 5 Apr 2016 at 19:36, Martin Packman
wrote:
> Some of you will be aware of the excitement over the last week getting
> Juju 2.0 into Xenial, this is an update mail so everyone knows what
>
Some of you will be aware of the excitement over the last week getting
Juju 2.0 into Xenial, this is an update mail so everyone knows what
the goal is with the user experience.
The challenge here is we want Juju 2.0 and all the new functionality
to be the default on release, but not break our exis
14 matches
Mail list logo
