I'm embarking once again on my periodic quixotic quest to corral all ebuilds
(Gentoo packages) for Trinity and combine them into a usable overlay.
Is anyone else (Fat-Zer?) still working on this?
If not, does anyone know of any old overlays with substantial material that
isn't in the following?
https://github.com/serghei/gentoo-trinity-overlay/ (Serghei's--long dead)
https://github.com/Fat-Zer/trinity/ (Fat-Zer's--still on 3.5.13)
https://bitbucket.org/mgebert/gentoo-trinity (dropped by author as of July)
(plus the one I was working on with Roman back in 2011, for which I
ironically have the materials but not the URL)
In particular, I'm looking for better post-kde-sunset support for the
packages still building with autotools.
I keep hoping that someone else will take up the torch on this, but everyone
who's tried seems to lose interest within a year or two, so I'm reluctantly
going to give it another shot. The intention here is to:
1. collect existing materials in one location
2. do appropriate version bumps as new versions of Trinity come out
(I'll be automating this as much as I can)
3. try to get *something* into the official overlays list and the Gentoo
wiki, so that people at least know it's there (an unfun but necessary step)
4. centralize efforts so that people interested in working on this don't
get mired down in version-bumping old ebuilds
I lack the skills, time, and energy to create the substantial number of new
ebuilds needed for a complete overlay. If anyone else offers to pitch in and
help with this, I will be *ecstatic*. (Otherwise, the only way forward may
be to offer cash incentives.)
Of course, I may get nowhere at all (again), especially since I'm currently
rebuilding my test environment after the xorg-server and xorg-driver
packages somehow managed to desync. :(
I'm having problems building libtdeldap for ARM. The build fails with
the following errors;
ldappasswddlg.cpp: In constructor
'LDAPPasswordDialog::LDAPPasswordDialog(TQWidget*, const char*, bool,
ldappasswddlg.cpp:36:96: warning: enumeral and non-enumeral type in
conditional expression [enabled by default]
ldappasswddlg.cpp:36:123: warning: enumeral and non-enumeral type in
conditional expression [enabled by default]
In file included from /usr/include/hdb_asn1.h:8:0,
../config.h:210:56: error: declaration of C function 'long unsigned int
rk_strlcat(char*, const char*, long unsigned int)' conflicts with
/usr/include/roken.h:146:42: error: previous declaration 'size_t
rk_strlcat(char*, const char*, size_t)' here
../config.h:222:56: error: declaration of C function 'long unsigned int
rk_strlcpy(char*, const char*, long unsigned int)' conflicts with
/usr/include/roken.h:143:42: error: previous declaration 'size_t
rk_strlcpy(char*, const char*, size_t)' here
strlcat & strlcpy don't appear to be defined anywhere until configure
is run ...............
checking for strlcat... no
checking if strlcat needs custom prototype... yes - in libtdefakes
checking for strlcpy... no
checking if strlcpy needs custom prototype... yes - in libtdefakes
.... and they are then defined in the subsequent config.h as folllows;
unsigned long strlcat(char*, const char*, unsigned long);
unsigned long strlcpy(char*, const char*, unsigned long);
...... which conflicts with '/usr/include/roken.h' as the error above
Anybody know how I resolve this correctly, without manually intervening
and modifying the auto-generated config.h?
On Mon, Dec 28, 2015 at 12:31:23AM +0000, Lisi Reisz wrote:
>On Sunday 27 December 2015 05:33:45 Mark S Bilk wrote:
>> On Sat, Dec 26, 2015 at 07:17:57PM +0000, Lisi Reisz wrote:
>> >> The K was originally suggested to stand for "Kool", but it was
>> >> decided that the K should stand for nothing in particular.
>> >Because of the horror that suggestion would have produced in some of us.
>> >I _could_ not have used something called "Kool".
In another message you seemed to associate the word "kool"
with the substitution of "u" for "you" by "the youth-aspiring
middle-aged". So perhaps you are horrified by the usage of
"kool" for what you perceive to be the same purpose by such
people? Correct me if I'm wrong.
That leaves "Ka".
>> >Mind you, the Ford Ka still seems to be selling. But not to me.
>> OK, now I'm really confused. The horror of "kool" might be due
>> to a dislike of language corruption. But what's wrong with "Ka"?
>> It has many different meanings, some of them thousands of years old:
>> It was part of the ancient Egyptian idea of the soul:
>> Lisi, please explain why "Ka" is repulsive to you and others.
>> Please use terms that don't require readers to have your
>> particular mental/cultural/ethnic context (whatever that might be).
>What is your age, nationality and education? (All relevant here.)
70, American, two years university and much independent study.
>If you don't understand, you don't understand.
Does that mean you don't intend to explain your dislike of "Ka",
because you think the reason for it is obvious? I hope you
will explain it anyhow.
Perhaps some other list subscribers would write in and say
whether "Ka" has any unpleasant associations for them?
>Or are you just being specious?
No, I am not lying.
-----BEGIN PGP SIGNED MESSAGE-----
On 2015/12/26 10:47 AM, Lisi Reisz wrote:
> On Saturday 26 December 2015 05:43:01 Mark S Bilk wrote:
>> and told not to find it via Google, etc.
> People DO look for things via Google. Trinity, as opposed to the original KDE-Trinity, was an unfortunate choice
> of name when it comes to search engines, and nowadays it usually does come to search engines. Perhaps determinedly
> call ourselves TDE _not_ Trinity. After all, the K in KDE didn't mean anything.
Trinity (not Trinity Desktop) is not a dangerous program. It is a kernel fuzz tester, that calls system calls at
random and it is intended to be used to spot bugs otherwise difficult to detect. Having said that, the name in not a
fortunate choice, since it partially match with Trinity Desktop Environment, which as raised by Mark it can generate
confusion among new users.
So we just need to make sure we always refer to TDE either as TDE or Trinity Desktop Environment or at least Trinity
As for the K in KDE, it initially meant "Kool", from which the make KDE.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
On this website:
is a Linux program that makes random system-calls. The
author calls it a "fuzzer" and has named it "Trinity".
When run, it creates lots of junk files, can delete
pre-existing files, and do anything else the OS can do.
A friend of mine wanted to install TDE, but carelessly ran
that "fuzzer" program instead. He cleaned out the junk files
but doesn't know what other damage has been done.
People need to be warned about that program!
I sent e-mail to the author asking him to put a warning
on his web page for people seeking TDE, but I don't know
if he will do it.
Prospective TDE users must be sent here directly:
and told not to find it via Google, etc.
Hi I run into an issue when building tqt and tde without opengl.
The build of tqtinterface fails with:
In file included from
/usr/tqt3/include/ntqgl.h:83:21: fatal error: GL/glu.h: No such file
# include <GL/glu.h>
As you can see it because GL/glu.h is not present on the system (which
should be ok for non-opengl build). I don't want to add yet another
build time dependency only because of excess header which doesn't
needed to produce any code...
AFAIK most of cpp files under the tqtinterface produce any useful code
so they may be safely removed only slightly changing the cmake
What do you think about both the issue and future of the tqtinterface?
PS: As I can see tqtinterface is a just a legacy by now, so may be
it's better to rid of it completely?
I've been building tde for various architectures (arm, ppc, amd64 ...)
and I've come across a couple of issues that maybe somebody could help
me with. This is using latest GIT source. I know I could just pull debs
from the net.
1. On debian jessie, after building, 'aptitude install tde-trinity'
The following packages have unmet dependencies:
kitchensync-trinity : Depends: libopensync0 (>= 0.22) which is a
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) kitchensync-trinity [Not Installed]
2) tde-trinity [Not Installed]
3) tdepim-trinity [Not Installed]
but, libopensync0 isn't available in jessie. Obviously, the packages
build because Slavek's repo was in the sources.list. So, what gives? It
shouldn't need Slavek's repo in the sources.list to install TDE should it?
2. On debian wheezy (yes, I know it's oldstable) tdelibs FTBS.
This is due to heimdal/krb5.h as C++ does not permit struct names and
typedef names to be the same or so I believe .... Patching krb5.h on
wheezy solves the problem.
Anyway, is that just a case of wheezy is dead long live jessie and folk
are not expected to build on wheezy/
Any info, especially regarding 1, greatly appreciated.
I wanted to have a look into the source code, but I'm not sure where I can
I found the list of the files from etch kdebluetooth
Can you help a bit please?
I am sure I have used it in Suse as well.
perhaps some few things can be reused and put together to enable bluetooth
The help documentation for kde3/trinity does not include information on the
katepart find/replace dialog "Placeholders" text entry box, checkbox or button.
Searching, I found where it was later added in KDE4.
A somewhat expanded version of that help is included below. I opened a eature
request http://bugs.pearsoncomputing.net/show_bug.cgi?id=2558 (dunno if Darrell
is still the help Maestro, so it is there for anyone to patch/submit - I don't
have a current clone of the repo or I'd do it.):
Here you may enter the text to replace the text or expression entered in
the "Text to find:" entry combobox.
You can reuse all or part of the "Text to find:" text or expression in the
"Replacement text" by selecting the "Use placeholders" checkbox. Placeholders,
also known as 'backreferences', are a special character sequence that will be
replaced with all or part of the original text or expression. They offer a
short-cut to entering a full "Replacement text" expression. For instance, by
default "\0" represents the complete 'pattern space' matched as a result of the
text or expression entered in the "Text to find:" box. (a backreference to the
entire matched string).
You may insert placeholders into the "Replacement text" box by clicking the
"Insert Placeholder" button, then selecting an option from the menu like
'Complete Match'. For example, if you are searching for "message", and you want
to replace it with messages insert the Complete Match placeholder and add and
"s". The replace field will then contain "\0s".
If Kate is installed, you can learn more about placeholders in the 'Regular
Expressions' appendix of its documentation.
David C. Rankin, J.D.,P.E.