tde-devels

devels@trinitydesktop.org

7 participants
3840 discussions

Darrell - Build Script Updates - go bys online?
by David C. Rankin 16 Jan '14

16 Jan '14

Darrell, I am having to go one-by-one through my build scripts for each tde package and remove old patches, etc. I don't know which ones are still needed. Eg (for tdebase): msg "Patching - tdebase patch set...." for patch in ${srcdir}/patches/*.patch; do _p=`basename $patch` msg "Applying patch $_p..." patch -Np0 -i $patch done Do you still have your build scripts online? I see you closed humanreadable.nfshost, so I'm looking for a current set of "go bys" to prevent repeated build failures figuring out which current patches I need :) Help a brother out? -- David C. Rankin, J.D.,P.E.

1 0

Re: [trinity-devel] Need debian help - what fixed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707417
by Darrell Anderson 16 Jan '14

16 Jan '14

>That fixed the FTBFS - Why the FILE_OFFSET_BITS=64?? There is no >way file size exceeds (2<<31)-1 bits?? I don't know. I only remember seeing the same build failure as you described. What I shared is the result of my repairs. Darrell

1 0

Re: [trinity-devel] Need debian help - what fixed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707417
by Darrell Anderson 16 Jan '14

16 Jan '14

>Will do, I also just built it with: > > cmake ../${pkgname}-${pkgver} \ > -DCMAKE_BUILD_TYPE=Release \ > -DCMAKE_SKIP_RPATH=ON \ > -DCMAKE_INSTALL_PREFIX=/usr \ > >-DLIBGSF_INCLUDE_DIR="/usr/include/libgsf-1;/usr/include/glib- >2.0;/usr/lib/glib-2.0/include;/usr/include/libxml2" My build script configuration: SLKCFLAGS="$SLKCFLAGS `pkg-config libgsf-1 --cflags`" SLKCFLAGS=" -D_FILE_OFFSET_BITS=64 $SLKCFLAGS" mkdir -p build cd build cmake \ -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \ -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \ -DCMAKE_INSTALL_PREFIX=/usr \ -DCMAKE_BUILD_TYPE=Release \ -DLIB_SUFFIX=${LIBDIRSUFFIX} \ .. Darrell

2 1

Re: [trinity-devel] Need debian help - what fixed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707417
by Darrell Anderson 16 Jan '14

16 Jan '14

>but for some reason cmake doesn't find it. I'm too dense to find >out where/why it isn't being use. Where do I look? I vaguely recall encountering the same failure about tree.h. After I found the patches I previously attached I then was able to compile wv2. Head to this URL: http://snapshot.debian.org/package/wv2/0.4.2.dfsg.1-10/ Download the file in the first link, which is a tar.gz. Open the tar.gz and notice the directory of patches. Use those patches to build wv2. That should resolve wv2 concerns. Darrell

2 2

Re: [trinity-devel] Need debian help - what fixed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707417
by Darrell Anderson 16 Jan '14

16 Jan '14

>Debian fixed a bug with wv2 I need to patch/fix for tde. The bug >was: > >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707417 > >How in the heck do you find out what debian did? I have never figured out how to find patches mentioned in Debian bug reports. I'm sure there is a method to their madness. Attached are two patches I use to build wv2. The patches only allow me to build wv2. I have no way of knowing whether wv2 is actually providing kword the necessary support because wv2 has been unsupported for a long time. Probably should be Yet Another Bug Report. Darrell

3 2

Need debian help - what fixed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707417
by David C. Rankin 16 Jan '14

16 Jan '14

All, Debian fixed a bug with wv2 I need to patch/fix for tde. The bug was: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707417 How in the heck do you find out what debian did? -- David C. Rankin, J.D.,P.E.

2 2

Re: [trinity-devel] Need debian help - what fixed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707417
by Darrell Anderson 16 Jan '14

16 Jan '14

>> All, >> >> Debian fixed a bug with wv2 I need to patch/fix for tde. The >bug was: >> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707417 >> >> How in the heck do you find out what debian did? > >Some problem with libxml was solved in KOffice - commit b6474af7. Yes, but David asked how to find patches mentioned in Debian bug reports. In the referenced bug report there are no links to an actual patch. Only a textual reference the problem is resolved. Darrell

2 1

Re: [trinity-devel] Final inspection for KDE-TDE/kde/tde rebranding issues
by Darrell Anderson 15 Jan '14

15 Jan '14

>I would like to inspect source tree text strings for instances of >KDE/kde rebranding issues and update to TDE/tde. Mostly in >tooltips >and What's This help strings. My challenge is being able to >efficiently grep only those strings, which often in the sources >are multiple lines. > >I would appreciate shell scripting advice to find such text >strings. Nobody knows? Darrell

2 1

Calvin - have you updated HAL to use eject from util-linux instead of the eject package?
by David C. Rankin 15 Jan '14

15 Jan '14

All -> Calvin, While I plan on building R14 without hal, taking a look at the package on AUR, hal still depends on eject. Eject now conflicts with util-linux, eject which means we need to remove eject as a dependency. Do you plan on updating, or should I just cannibalize it? -- David C. Rankin, J.D.,P.E.

2 4

Missing help handbooks
by Darrell Anderson 15 Jan '14

15 Jan '14

All, With respect to the recent conversation about helping the Trinity project, here is a list of apps that have no help handbooks: kdevdesigner (tdevelop) kstreamripper tderadio ksquirrel ktorrent kbarcode kbarcode-single kbarcode-editor kbarcode-batch kbibtex kpalmdoc (kpilot) dolphin kiosktool kvaio (kcontrol module) thinkpad (kcontrol module) kcmview1394 (kcontrol module) display (kcontrol module) kmobile (tdepim) All of the apps have had no help handbook since the KDE3 days. If you enjoy using one of those apps and want to help, please consider writing something. You do not need to deal with docbook. If you send me a text file I will massage the information into a help handbook file. The text need not be a novel. Sometimes a few paragraphs is sufficient. For most handbooks, a description and highlighting the main features is a nice start. Thank you! Darrell

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels