On Sun 2018-10-07 10:31:13 +0200, intrigeri wrote:
> intrigeri:
>> What matters to me is the users' perspective. I think we should
>> provide a clear, unambiguous transition path and avoid leaking
>> technical details to users. So once MAT2 reaches feature parity with
>> MAT (I think the only real blocker is the lack of a Nautilus
>> extension; MAT v1's seems to be broken on sid currently but it has
>> a GUI which mitigates that problem) I think we should:
>
>> - Have mat2 conflicts+replaces mat, remove mat from testing+sid,
>> and ship a transitional package called mat that pulls mat2 in.
>
> IMO we should do that as soon as mat2 installs the Nautilus extension
> (#910491).
>
> Does this make sense to you? Is there a better way to handle this?
this all looks reasonable to me as well.
thanks for staying on top of it.
--dkg
