Re: Removing offlineimap?

[Greg Troxel <gdt%lexort.com@localhost>]

Thomas Klausner <wiz%gatalith.at@localhost> writes:

> I've just imported offlineimap3.
>
> I plan on removing offlineimap (using Python 2) in a week, unless we
> find any active users (that can't switch to offlineimap3).

Why did you import offlineimap3 instead of just updating offlineimap?
We generally only have multiple versions when there is a good reason,
and if it's expected that users can generally just update, then not
having multiple versions is better.

Perhaps the logic is about python2, but surely we do not accomodate
people who want to use only pyhon2 and object to having python3.x on
their system.  Using python2 is today a bug, and moving away from it a
bugfix.

Reading the packages and homepages, it's really unclear what's going on.

"offlineimap3" is at version 8.

The name of the package is not changing, but there is a new repo.
There's no "ng" or similar.  It's under the github organization, so
clearly it's authorized/official.

The user-facing parts of the package are labeled OfflineIMAP in docs,
and the installed programs are simply offlineimap.

I conclude that this is simply the next version of offlineimap from the
same upstream, and that for no good reason the git repo used for
development has a 3 suffix.

Thus, the package should remain as offlineimap, with no 3, and just
fetch from the (misnamed) repo.

Upstream says config files have not changed, so this should not be a big
deal.

So why not delete the new package you just imported, updated
mail/offlineimap (to the new package contents), fix DESCR to say what's
going on, and call that all normal?