Hi Chris,
We always needed that. I like 2 better than 3 just because of backwards
compatibility.
3 seems fine as well just that CI setups/scripts will have to change
accordingly.
Regards,
Vipul Rahane
On Mon, Aug 5, 2019 at 2:08 PM Łukasz Rymanowski <
lukasz.rymanow...@codecoup.pl> wrote:
>
Hi Chris,
I'm with you on 3)
Best
Łukasz
On Mon, 5 Aug 2019 at 22:59, Fabio Utzig wrote:
>
>
> On Mon, Aug 5, 2019, at 3:30 PM, Szymon Janc wrote:
> > Hi Chris,
> >
> > Yes! I'm also for option 3. Lets deprecate for next (1.8) release (make
> > those print proper warning info when used) and
On Mon, Aug 5, 2019, at 3:30 PM, Szymon Janc wrote:
> Hi Chris,
>
> Yes! I'm also for option 3. Lets deprecate for next (1.8) release (make
> those print proper warning info when used) and just remove for 1.9.
+1
Hi Chris,
Yes! I'm also for option 3. Lets deprecate for next (1.8) release (make
those print proper warning info when used) and just remove for 1.9.
On Mon, 5 Aug 2019 at 18:47, Christopher Collins wrote:
> Hello all,
>
> The newt tool supports three "project commands":
>
> * install
> *
Hello all,
The newt tool supports three "project commands":
* install
* upgrade
* sync
I always have a hard time remembering the particulars of commands like
these. For example, when other package management systems support both
"update" and "upgrade", I inevitably mix them up. I propose we
