Tails

#8 Updated by intrigeri 2015-10-05 05:57:19

I wonder if we should turn a persistent preset (i.e. something that one can see in the persistent volume assistant) into a manual one. Perhaps we need to have Feature #9499 at the same time as this one? In other words, do we want to do Feature #9498 in 1.7 or in 1.9?

#10 Updated by anonym 2015-10-07 06:31:21

intrigeri wrote:
> I wonder if we should turn a persistent preset (i.e. something that one can see in the persistent volume assistant) into a manual one. Perhaps we need to have Feature #9499 at the same time as this one? In other words, do we want to do Feature #9498 in 1.7 or in 1.9?

I do not think we have to replace it. In 1.7 I think we should have both presets activated (with claws’ implying activation of icedove’s, i.e. the current situation), plus provide manual steps for cleaning up the claws one. 1.9 can be the last release we link to these instruction (and the migration instructions in general) in the release notes. No code changes needed. At some point we may want to clean up the enabling code from live-persist (we still have code for: Migrate Squeeze-era NetworkManager persistence setting to Wheezy :)).

#12 Updated by sajolida 2015-10-07 08:25:34

I’m not sure we should “replace” one with the one or do to many automated steps here (as this could create misunderstandings or complicated setups during the transition, need cleaning, etc.). Instead what about having both Claws and Icedove in t-p-s until Claws is removed? People should active Icedove or deactive Claws manually as instructured. That’s more explicit to the user to the cost of being more noisy on the interface (for a couple of releases only).

Once we’re in Tails Jessie, we can maybe automatically remove or delete the persistence line about Claws and warn the user about it (unless we think it’s a valid usecase to stick with Claws in Tails Jessie).

#13 Updated by intrigeri 2015-10-12 05:52:01

> Instead what about having both Claws and Icedove in t-p-s until Claws is removed? People should active Icedove or deactive Claws manually as instructured.

Sounds good.

> Once we’re in Tails Jessie, we can maybe automatically remove or delete the persistence line about Claws and warn the user about it

I personally see little value in putting any time into removing that config line, and it implies some work + some risks.

> (unless we think it’s a valid usecase to stick with Claws in Tails Jessie).

Please, no :)

#14 Updated by anonym 2015-10-17 07:51:35

intrigeri wrote:
> > Instead what about having both Claws and Icedove in t-p-s until Claws is removed? People should active Icedove or deactive Claws manually as instructured.
>
> Sounds good.

I think we’re all agreed then.

> > Once we’re in Tails Jessie, we can maybe automatically remove or delete the persistence line about Claws and warn the user about it
>
> I personally see little value in putting any time into removing that config line, and it implies some work + some risks.

Agreed. Let’s put instructions for how to clean this up (once the user has migrated the old Claws stuff, potentially) in the manual instructions.

> > (unless we think it’s a valid usecase to stick with Claws in Tails Jessie).
>
> Please, no :)

Agreed, let’s not. So far it’s been a bunch of poorly integrated bugs that happens to have emailing capabilities. I do not want to continue supporting it.