[Pkg-privacy-maintainers] Bug#910493: Handle transition from MAT to MAT2

[intrigeri]

Package: mat2
Version: 0.4.0-1
Severity: normal

Hi,

let's discuss how we'll be handling the transition from MAT to MAT2
in Buster. My goal here is to avoid users keeping using the
deprecated, unmaintained MAT v1, and to nicely transition them to the
new MAT2 implementation.

As I wrote on the ITP (trimming down ideas that don't make sense
anymore):

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?

Cheers!
-- 
intrigeri