At the Nuremberg sprint, I saw a demo of juju status that produced tabular format by default. I'm guessing that this issue means that can never actually be enabled.
Although... it could be done backwardly compatibly (with a required environment variable or configuration file setting) and perhaps that shows the way forward here. We could allow a user to change a setting that enables backwardly incompatible features (such as removing environment fallback or producing tabular format status). That doesn't help with the code cruft issue though. On 30 April 2015 at 11:29, Michael Hudson-Doyle <michael.hud...@canonical.com> wrote: > I don't want to bore on and on about this, but one thing. > > On 30 April 2015 at 22:06, Nate Finch <nate.fi...@canonical.com> wrote: >> If someone needs 1.18 CLI compatibility, they can use 1.18. It's that >> simple. > > It's not that simple to do that though, as long as new versions of > juju go into trusty-updates. You'd have to pin the version or do > apt/preferences junk to prefer trusty over trusty-updates for > juju-core or something. I'm not even sure, and I'm much more familiar > with this sort of thing than it makes sense to assume our users are. > > Cheers, > mwh > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
