--Sig_/PlLrW/CU7q3LBmBLtZURrn2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, 09 Jun 2017 09:49:44 +0200
Ren=C3=A9 J.V. Bertin <rjvbertin@gmail.com> wrote:
> >And you're already adding the wrapper for all KF5-ports. =20
>=20
> True, but only for starting them from the commandline.

Yeah, that's another thing I might quizz you about, later. I'll
certainly want RKWard to load its icons regardless of how it was
started...
=20
> >Then, why not just make all ports of kf5 applications depend on it,
> >and get sane behavior out of the box, without pushing the
> >responsiblity to read up on all this to the user?
>=20
> I find it's still a bit early for that without having more feedback
> from the field. The problem is also that both the Applications and
> Plasma categories contain applications and libraries. Setting a
> platform theme plugin as a dependency for a library feels a bit
> unelegant, and I don't really want to have to remember declaring it
> manually either :)

I can see there are corner cases. But it's fairly important: I don't
think there is any KF5-application that is better off without any
icons. And in fact, both as an application maintainer and as a user,
that's definitely something I would expect packaging to take care of.

If that means adding an unnecessary dependency to a few
libraries/subports, I would consider that the lesser evil. (Also keep
in mind, that at least for the time being, the primary dependents of
frameworks libraries are KDE applications, anyway).

> >Sure, I suppose a select few KF5-applications may want to play
> >different on Mac, but then _those_ would be special cased, while
> >all =20
>=20
> What do you have in mind?

I'm absolutely not up to speed on MacPorts but could you make it such
that any port that has kf5.add_app_wrapper in it will also get a
dependency on kf5-osx-integration. Then only in those -
hypothetical?(*) - cases, where this is not desired, you'd add

  depends_lib-delete port:kf5-osx-integration

or something.

Regards
Thomas

(*) Are you aware of any applications among your kf5 ports which would
_not_ want kf5-osx-integration?

--Sig_/PlLrW/CU7q3LBmBLtZURrn2
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJZOn8iAAoJEDkVkd8YWMu2SlMP/RWX4i7QxeVcguX3LUbdayz6
bpbaK7KoVrskM18jJLKcc8O99WMZ056Txd/swNUFgPy5oc7p/R5JF3qdDLSwQBNZ
VtzQD9JAnceZfFkrH9ISZnThPPzs9FgsOVWqr5KVuwxdVQJS+TS5J0snUqLRKcEQ
h0ZdnhXMBZz6wEqHqt3wH10K7FrYxNdc+FcZ7RGwlOHjS+akW0ez/3JVE7XwIW1K
aDwpb7U8snr2Kh0xQF8igJIo0gxTTEcuhSPmB6fcQbv893bHIlNvCeoCLdMStGIH
OiZKV0zRDJnor6ukp0SXpJryIwoItYZFBUcVvrX7RcmhN9mjBVlA0uGDgJycO1Ph
z+A1IapV8DiqUb/ZyCf7oo93tGqGSSWL76jw+Xre0vcr7AC4Gfct+jh/Q/NFy5MN
UI9b4qsgL5Ye6tb2VoAD6F2sEXVc7JOlwFwJ/c5QbWAS5WhTOLYtNJi3NlGNO0OD
jE6oGyTujwrZfKQKhybs3P68gsWLVQ6UQ6p2cY7RudfmUZpKha9IPyLH6Tb+Vg8w
R7/9jZwUmmMyjRowJqiQ5vfLxL+lrvLav8HGs8ON5hHDi6MGrPwBwW43JWGRV0Be
NxLR5B4sorYOrYNzFvN0XR04AXAo661Jt6huPW8jT3tBt6+6LriMTPPVAuAFgGKO
xwjItFvS//AxIsi+kcDz
=3DKq
-----END PGP SIGNATURE-----

--Sig_/PlLrW/CU7q3LBmBLtZURrn2--