1 Oct
2018
1 Oct
'18
9:31 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2018/10/01 02:20 PM, David C. Rankin wrote:
On 09/07/2018 03:39 AM, Michele Calgaro wrote:
Hi David,
the major reason for qt->tqt and kde->tde rename is avoid package conflicts in case
tde is installed together with
others DE. A lot of renaming has alrady been done (and a lot still has to be done), but at
this stage going back is
probably as much work as going forward.
It feels good for TDE to have its own identity, so I see rename as a good thing. Just my
two cents, others may have
different views on this.
Cheers
Michele
Dear all, in the next days/weeks, Slavek and I
will be doing some qt->tqt renaming in the master branch. This
may affect package building and cause unwanted FTBFS or may require adapting your
building scripts. The R14.0
branch will not be affected by these changes.
Cheers Michele
Michele, Tim, Slavek, All,
With KDE going to Plasma and Qt going to Frameworks, is there still any need for the
Qt->tQt changes? I'm just
trying to stay up to date. If we are still protecting for the possibility of a change in
Qt that the tqt layer
would handle, then that all makes sense, but if TDE plans to continue maintaining Qt3
(which I see no reason to
change, it does everything I need), then is there still a need for the renaming effort?
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAlux6XYACgkQKnW3yore
1c++WA//eJBIYnwWDdI+xF40vFgOdpzmIJEHsb1qrghhcwZGJhbL1SWa3WnSEVY1
5qMw/9oz8YXlZVCrRBvSLY/Yh9Fs7pHeJpgHUSHRmaJ9RGxBbfMl2V0YluhXnYvF
Pcuwim8icfQWC4foZj8vggkWNaisSjfiE5QkQQU1P+5Zm2hgNHotIiet5doluSzO
OKl/941QDd4YUpLVy55efI7uoAaiRTHWt461T1dqGXwY+FVIgPiXdNZzvVWg96hk
ixxxDkvfPWpffXyQikd4EuDtUsy/RB8YCLreAUlqBGMJPfONslkP9FxQef4IziHD
S4IqXjSFvg2RuOCxRZdfJLOuOtMzku2OSP0rKjbmCXl/STRUwcsmbJWJce+FCS0k
o/pzjTMHobHf0gQeAhAgM3F/OETwYesq3tYHMnp+iSmHT0k/WpqOZPSyIwocr74x
4+dFasbn5R97sDIYLp9SS1Q7rFqOC8x0RDJZRFom3s62kM41o8sVQOp9xlF0P0dz
WouGDNq4/0MxQyh+erprgulQgWr9GMH3Vpk9kOzTGv5LclB6aBjLL6wOK+oVGgdP
OmMEWcYwucUgGuslED7CuRq64hvS1VFPWL/OtpBCoJxPaCkDAOr9twtk1NaIOStz
urEN5+vtUwuI61sEdI4TVX6sTl68/ZONFTtJtSx7dOB4YhO5csI=
=0TDQ
-----END PGP SIGNATURE-----