[Users] Consider packaging claws-mail as flatpak distributable?

[Danny van Heumen]

To follow up:

Most of the flatpak packaging issues are tackled. I need to do some work for clean-up after building, but that's the biggest obstacle so far. We're working on finishing up a first iteration.

See in-line for further comments ...


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, September 1, 2019 11:49 PM, Danny van Heumen <danny at dannyvanheumen.nl> wrote:

> Hi all,
>
> A quick follow-up. I've got a preliminary first version of the flatpak
> manifest for Claws-Mail. This currently includes all but the
> python-plugin. It does still have some issues to be resolved.
>
> https://github.com/flathub/flathub/pull/1140
>
> A few questions regarding this work as I am finalizing and aligning
> with the Flathub people at the same time:
>
> 1.  I currently deploy mostly newest releases of dependencies.
>     Would that be okay or would the preference be to strictly follow the
>     versions of e.g. the debian package? (I would personally prefer newest
>     as that is the benefit of having flatpak.)
>
> 2.  When finalizing packaging on Flathub, would you as Claws-Mail
>     developers want to have write-access to the github repo too? (It would
>     be preferred, as I am not directly affiliated with the team.) If you
>     let me know a few github user accounts, I can add them to the PR.)

Ad. 2. Please provide some github user-names to add, such that the original Claws-Mail team members preserve some control over the flatpak packaging instructions. I will remain active, regardless.

> 3.  Does claws-mail require access to directories outside of $HOME?
>     Currently I have identified '~/.claws-mail' and '~/.bogofilter'. I'm
>     not sure if other plugins still need specific directories to be
>     accessible.

Ad. 3. Any further input on this? I am not that familiar with other plug-ins, but first impressions tell me that most plug-ins work inside the ~/.claws-mail directory.


>     [..]


Kind regards,
Danny