While reviewing the upcoming patch set for LIB_K* -> LIB_TDE* I noticed some things.
There are a handful of spots in the sources where readEntry looks for X-TDE-* || X-KDE-*. We can't blindly change all such occurrences because many are legitimate, such as the tdebase/applnk files that support KDE4 menus and some occasional spots where code is supporting both TDE and KDE4 (such as su). Yet I think in many of those || tests we can eliminate the test for readEntry X-KDE-*.
I don't see this as an urgent issue and I'll open a bug report if asked. We can resolve those || tests in R14.0.1 or R14.1.0.
Comments? Thoughts?
Darrell
While reviewing the upcoming patch set for LIB_K* -> LIB_TDE* I noticed some things.
There are a handful of spots in the sources where readEntry looks for X-TDE-* || X-KDE-*. We can't blindly change all such occurrences because many are legitimate, such as the tdebase/applnk files that support KDE4 menus and some occasional spots where code is supporting both TDE and KDE4 (such as su). Yet I think in many of those || tests we can eliminate the test for readEntry X-KDE-*.
I don't see this as an urgent issue and I'll open a bug report if asked. We can resolve those || tests in R14.0.1 or R14.1.0.
Comments? Thoughts?
Darrell
Not for R14.0.0, but we can look into it for R14.1.0. We will need some degree of upstream cooperation in various projects so as not to break things like automatic tdesudo prompts for administrative programs.
Tim