[RFC] Smoother upgrades

[Vincent Ladeuil]

>>>>> "Jelmer" == Jelmer Vernooij <jelmer at samba.org> writes:

<snip/>

    Jelmer> I think this operation is common enough to be
    Jelmer> runnable after upgrade (but only if the upgrade was
    Jelmer> successful).

The message displayed after upgrade can mention that, if it's
only an option of upgrade you leave my use case (keep backup
longer) out.

    Jelmer> If we separate them users might end up removing
    Jelmer> backup.bzr in places where the upgrade was not
    Jelmer> succesful and end up losing data.

I'm not sure I'm following you there, you want an upgrade option
to delete the backup as soon as the upgrade is successful but
then you worry about users deleting it in case of errors ?

I'd rather say that people who will blindly delete backup.bzr are
more likely to use that upgrade option or any recommended
command to delete it, no ?

    Jelmer> As a side-note I think 'bzr clean' is a confusing
    Jelmer> name. The name doesn't really indicate how it is
    Jelmer> different from 'bzr clean-tree' and git has a 'git
    Jelmer> clean' command that behaves similarly to 'bzr
    Jelmer> clean-tree'.  I much prefer 'bzr garbage-collect'
    Jelmer> (did that have the same function?) that was proposed
    Jelmer> earlier.

Yes, I was [thinking about garbage-collect/agree it's a better
name], not clean, sorry for the confusion.

    Vincent