>I am fine with both versions. I think the second one misses the
>point that TDE is a DE which puts productivity before fancy-
>useless-bothering visual effects, which I think is the main reason
>why people use TDE. Perhaps the following version is a little
>better:
I understand your feelings. :)
A goal of a press release is to offer a positive spin and focus on
the announced product rather than what other products lack. We want
to refrain from KDE bashing. If you browse the dev mail list
archives from a while ago, you'll discover that a couple of KDE
devs invited themselves into our mail list and started a nasty
spitting contest. Got rather heated. Nobody won and one of the KDE
devs took to his blog to continue bashing Trinity. He stopped that
public campaign when a lot of people posted comments to his blog
entry to leave us the hell alone, that the free/libre software
philosophy allows and embraces forking. He was reminded that we
were not harming anybody. After those public rebuttals he stayed
away, but I have not forgotten him or his tirades.
I'm not afraid of bashing KDE4, especially the piece of shit known
as akonadi, or the obvious relentless fan-boyism that permeates the
entire KDE culture. Yet I'd rather we follow the advice of
Voltaire's Candide and just "tend our own garden."
>------------------------------
>"Recently I discovered Trinity. I immediately felt at home with
>this traditional computer desktop environment, which focuses on
>productivity rather than the latest development in visual effects.
>In these days of tablets and smart phones, traditional desktop
>environments still play important roles. The TDE development team
>is friendly and anyone such as myself may contribute to preserve
>and enhance this fantastic desktop environment." --- Michele
>Calgaro, Italy
>------------------------------
>
>Feel free to massage it again if you find it appropriate.
Looks fine and thank you. Subject to final review by other team
members of course. :)
Darrell
Dear all,
since last September (October?) when I copy/move/delete files I see a window like the one in the attached picture.
I recall in the past I used to see a window with a progress bar and some buttons, likely containing the same information but much nicer.
Any idea?
Thanks
Michele
>Please take this discussion off-list. How ironic that a positive
>PR thread will end up damaging TDE even more in the PR arena.
Yes, you are correct and my apologies. I stand by my opinion ---
that was expressed in an opt-in subscriber-only private mail list,
but I should not have shared that opinion here.
Darrell
>> Some FTBFS fixed in GIT hashes:
>> + 719b6175: tdebindings
>> + b045832a: python-trinity
>> + 4f63e9fa: libtqt-perl
>>
>
>FTBFS in pytdeextensions and tde-guidance was fixed after
>successfull rebuild python-trinity.
Looks good here. Thank you!
That leaves rosegarden and tde-style-qtcurve.
Darrell
>Any clue ?
Yes, I have a clue. :)
A handful of apps don't compile after the recent API changes these
commits:
523c1fd9 2013-12-22 [tqt3] Automated update from Qt3
d1b6b7be 2013-12-22 [qt3] Repair performance regression
accidentally introduced with new style API
Tim is aware of the build failures.
The apps that don't compile with error messages related to the
style API commits:
python-trinity
pytdeextensions (probably only because of the dependency on python-
trinity)
tdebindings
libtqt-perl
tde-style-qtcurve
rosegarden
If you are a code hacker, look at these commits to create similar
patches:
a5826757 2013-12-23
7f8e73d6 2013-12-22
I tried patching python-trinity but I still kept getting build
failures.
Darrell
> What exactly is required to switch to quilt format? Is this a simple
> change to the dpkg-buildpackage call or something more complex?
Tim,
I don't have the experience of Slavek (so I may be missing something), but switching to quilt will require:
1) change the format inside debian/source/format from native to quilt
2) switch debian/ubuntu specific patches to quilt format
3)bremove anything related to quilt from debian/rules
4) modify the building scripts to create a "<source package>_<upstream version>.orig.tar.gz" file from the package source before building
5) modify the building scripts to build using format 3.0(quilt), which requires the .orig.tar.gz file to be in the parent directory of the debian folder
I have just updated dpkg on my Debian/Jessie, so in the next few days I will have to work on this, because I have already experience build failures, as Slavek initially mentioned.
If I find some other changes that are required, I will update the post.
Here are a couple of useful links as well:
https://wiki.debian.org/Projects/DebSrc3.0#Advantages_of_new_formatshttps://wiki.debian.org/DebianMentorsFaq#What_is_the_ifference_between_a_na… - section 2.4
Cheers
Michele