yb init is confusing because it has two overloaded meanings

[chris-laplante]

We've had some internal confusion over yb init because it does two different things depending on the context:

1. In a Yocto environment (i.e. bitbake is a valid command in your terminal), it upgrades your env to a yb env.
2. Otherwise, it creates a new yb env and a new yocto/ directory.

It's pretty easy to forget that you have an activated Yocto env. For example, you may cd somewhere else entirely from where your Yocto env lives. In this case, you probably want behavior #2 but what you're going to get is #1.

I think it is early enough in the lifecycle of yb that it makes sense to make a breaking change to resolve this confusion. What I'm proposing is to add a new command, yb upgrade, which will only do #1. yb init will be changed to always initialize a new yb env (i.e. #2). It will issue a warning (and maybe ask for confirmation) if it detects that you may have wanted to use yb upgrade instead.

[chris-laplante]

Fixed in 0.0.12