tde-devels

devels@trinitydesktop.org

2 participants
3755 discussions

by E. Liddell

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. :( E. Liddell

9 years, 1 month

In need of automake

by deloptes

Hi all, I need to put a check on a header from within automake project. How do I get this header found for TDE? FOOFOUND=yes ... AC_CHECK_HEADERS(foo.h, [], [FOOFOUND=no], []) thanks in advance

9 years, 1 month

[trinity-devel] nothing like kinfocenter in r14 menu

by Felix Miata

Why? Aptitude and Synaptice searching for ~infocenter for TDE also provides nothing resembling KDE's kinfocenter in Jessie. :~( -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

9 years, 1 month

libtdeldap fails to build on ARM

by Michael Howard

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, 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, from /usr/include/hdb.h:44, from libtdeldap.cpp:56: ../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 states. Anybody know how I resolve this correctly, without manually intervening and modifying the auto-generated config.h? Cheers, Mike. -- Mike Howard

9 years, 1 month

Re: DANGEROUS LINUX PROGRAM CALLED "TRINITY"

by Mark S Bilk

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". Lisi, 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: >> >> https://en.wikipedia.org/wiki/Ka >> >> It was part of the ancient Egyptian idea of the soul: >> >> https://en.wikipedia.org/wiki/Ancient_Egyptian_concept_of_the_soul#Ka_.28vi >>tal_spark.29 >> 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. Mark

9 years, 1 month

Re: [trinity-users] DANGEROUS LINUX PROGRAM CALLED "TRINITY"

by Michele Calgaro

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 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. > > Lisi > 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 Desktop. As for the K in KDE, it initially meant "Kool", from which the make KDE. Cheers Michele -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJWfoRmAAoJECp1t8qK3tXPIvoQALa8iv5Jtreb6vfL+gPecXVC SFhoz7NTxC/ojcvlLN6PO9uKDrye+jfchyeoApe42FndxjQS3qV6OrNeVj7vTMNt pUci38QKX8NZywLLmKLpUaWkfaJ1Ffzq6GjlINUFNRi/C+0QV67LRoKjFojWeawb bH6PRWIfgEcZ8/3D766BIsmZgRFEKKBnDiu7oEcgpxVOgIRNgMtrOeBrvhPvQ4+H byY58Peq6WttXcutnqZRe6IsTTXfiolqxAp9pLXTIZvj27Jl0TFa7EU9l/5ZGs9U RhnzjpbEvH/r7hvdE4tQWuC3fuEDIF6Lqkzlu2f8X7yahioDfwo9cZmNt7wCUw08 HBEWfO9i9iwT7QNTqNOPHEuK8vsWFcV9NqKr0Y75mAk/auYBr/Fg6mBkdfg/+P8z ON6qBqabkoNV41y8M5oWAWEtYs0TeDscHfQOMl9EoYc/BHOKAltTyAO0a2WmvRgu +eNbeDqJzkV87uxdA5rTbDTLcBQrOenGc8wlZ8bJBMP1PtjyYBMduIexauz8KoVR 89/2Cfo5uYm8Acxvx4Feh57BJAHC5njzowHWyNUhdXtBx8tvHkk7TLKVL8Y/PGW2 uc9TBVmMVBkfxrKVaEwKYs325N6OQzy2ymRtVkImT47b5nS83JiFfr4aGMg9BHo6 lVXsLTUURKgYd567QB/r =Cj1S -----END PGP SIGNATURE-----

9 years, 1 month

DANGEROUS LINUX PROGRAM CALLED "TRINITY"

by Mark S Bilk

On this website: http://codemonkey.org.uk/projects/trinity/ 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: http://trinitydesktop.org/ and told not to find it via Google, etc.

9 years, 1 month

tqtinterface and tqt build without opengl issue

by Fat-Zer

Hi I run into an issue when building tqt and tde without opengl. The build of tqtinterface fails with: === In file included from /var/tmp/portage/dev-qt/tqtinterface-9999/work/tqtinterface/qtinterface/interface_tqt3/tqgl.cpp:23:0: /usr/tqt3/include/ntqgl.h:83:21: fatal error: GL/glu.h: No such file or directory # 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 files... 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?

9 years, 1 month

Merry Christmas !

by Baron

A very merry and happy Christmas to all. Thanks in particular to the Trinity team for a great Desktop Enviroment. Looking forward to 2016 with great expectations. -- Best Regards: Baron

9 years, 1 month

tdepim/kitchensync unmet dependencies + krb5.h on wheezy

by Michael Howard

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' complains with; The following packages have unmet dependencies: kitchensync-trinity : Depends: libopensync0 (>= 0.22) which is a virtual package. 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. Cheers, Mike. --

9 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels