Hej,

Am Mittwoch, 11. Juni 2025, 21:09:17 CEST schrieb Soren Stoutner:
> On Tuesday, June 10, 2025 2:25:45 PM Mountain Standard Time Matthias
> Heinz
> wrote:
> > During a recent upgrade kmail lost the functionality for me to
> > display/parse meeting invites and I was just seeing them as inline
> > text. I really thought this was a bug in kmail, but had no time to
> > investigate further until now.
> > 
> > Today I found out that I was missing kdepim-addons. Sometimes in
> > past a necessary library seems to have been moved there. Or maybe
> > the package was newly created? I'm not sure.
> > 
> > But imho kdepim-addons should be a dependency for kmail, not just a
> > recommendation, to prevent other users from my experience.
> 
> I’m not sure I would agree with that.  Depends are the packages
> required for the core functionality of the package, which in the case
> of Kmail is sending and receiving email.  Recommends are the packages
> necessary for the ancillary functionality of the package, parsing
> meeting invites being an example.
> 
> Based on your description, my sense is that the current dependencies
> are correct.  Those wanting all the ancillary functionality of Kmail
> should install all the recommended packages, either by manually
> installing them or by automatically installing all recommended
> packages.

I agree with Soren here.

Setting a hard dependency on an addons package feels quite wrong. I 
believe that a Recommends is the best solution here. The package gets 
installed by default, but can still be removed by those who do not want 
it.
If you're not installing recommend packages, then you'll have to live 
with the occasional missing feature.

At the same time, if we were to set kdepim-addons as a hard dependency 
for kmail, then I'm sure some user would complain that they cannot 
remove an optional addons package they don't want.

At this stage I see little reason to change the current behaviour.


-- 
Med vänliga hälsningar

Patrick Franz

Reply via email to