I added tqca to the source tree. This module is from the original qca-1.0 sources with the TQt layer added. Adding the sources resolves bug report 817.
Building the package is much the same as with the original qca-1.0 package. The core of the configuration:
export PREFIX=/usr
export LIBDIR=/usr/lib${LIBDIRSUFFIX}
CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--qtdir=$QTDIR
make $NUMJOBS VERBOSE=1 || exit 1
make install INSTALL_ROOT=$PKG || exit 1
/usr/doc files:
COPYING INSTALL README TODO
I install TQt3 to /opt/trinity. I install both tqca and tqca-tls to /usr rather than /opt/trinity, but I don't think the installation location is critical.
I am building the package just before building tqca-tls.
I have no clue how to test the package after installation. Then again, I have no idea how to test tqca-tls either.
The tqca package requires about 5 seconds to build. Thus, troubleshooting should be a snap. For once. :)
Darrell
Hi all.
At the meeting we discussed that would be a good release official update
for 3.5.13 soon. In connection with the fact that 1 May it be just half a
year since the release of 3.5.13, it occurred to me that it could be a
nice term for the release official updates.
Therefore I would like to discuss with you:
__1__
Is this term too soon?
Can it be manageable?
Which patches to wait?
Already have poised:
+ patch to close #372
+ other patches from #675
+ workaround for #922
+ waiting for a patch for #258
+ considering revert patch for #394
I would like (but want to wait?)
+ fix SAK. Does anyone work on it? Or temporarily turn it off?
+ find a solution for #812
+ find a solution for #744, #615
__2__
Giving an update the new version number?
Apply here mentioned a few times R13.1 (or R13.1.0)?
They should be in this case, the patches in their own branch in GIT?
Change the version number in the names of all packages (some are otherwise
unchanged)?
Or just change the version number within kdelibs and file names leave them
unchanged?
Or simply release already prepared packages without changing the version
number?
What do you think?
I look forward to your comments
Slávek
--
This is my list of build issues. This is not a comprehensive project list. For example, I have not yet had to tackle gcc 4.7 issues.
There is a pattern to these bugs. I suspect once one bug is resolved, then similar bugs follow.
Blocker:
948 rosegarden: FTBFS when liblo is not installed
946 kstreamripper FTBFS
920 avahi-tqt FTBFS
872 tdesdk FTBFS Against TQt3
871 tdeadmin FTBFS Against TQt3
817 tqca: No tqca package exists for the new tqt3
790 kdemultimedia: audiofile.h configure errors
788 Kdemultimedia: Kaudiocreator won't build unless configure finds the cdda headers
597 tdebindings will not build without numerous patches
Critical:
942 k3b: Can't find the TQt version of the dbus-1.0 headers (install dbus-tqt to /usr)
913 Kerberos support does not exist with any cmake converted package
873 gwenview will not build libmng support
598 tdenetwork will not build on Slackware with wifi support
Major:
945 kpilot FTBFS: Can't find tqt headers
943 kmplayer: Can't find the TQt version of the dbus-1.0 headers (install dbus-tqt to /usr)
877 tdeutils: X11/extensions/extutil.h: present but cannot be compiled
818 amarok: Several build options missing with the cmake conversion
Normal:
950 rosegarden: Sym Links Incorrect
940 kile: Sym Links Incorrect
939 knights: Sym Links Incorrect
933 krusader: Sym Links Incorrect
932 tellico: Sym Links Incorrect
931 kmplayer: Sym Links Incorrect
930 kdiff3: Sym Links Incorrect
627 kspell Sym Link Incorrect
626 konversation Sym Links Incorrect
613 kipi-plugins Sym Links Incorrect
347 amarok Sym Links Incorrect
Minor:
947 kbarcode: unknown icon type
937 kradio: unknown icon type
935 krename: unknown icon type
934 krusader: unknown icon type
807 tdeaddons: unknown icon type
806 kipi-plugins: unknown icon type
805 tdeutils: unknown icon type
804 gwenview: unknown icon type
719 koffice: unknown icon types
Darrell
All,
I have written a brief draft document with some of the rationale behind
the TQt interface layer and the TQt conversion on the Wiki here:
http://trinitydesktop.org/wiki/bin/view/Developers/TQTRationale
Thank you to all who have (gently) reminded many times to get some kind of
rationale written up. The current document is not complete, and I welcome
questions and corrections on the provided Etherpad so that I may address
all concerns from the developers here on this matter.
If this works out, and I think it will, we will have features that no
other KDE 3.5.10 fork can ever attain. Please keep this in mind before
ripping into the implementation details; I took a significant risk in
doing this and I am already seeing benefits in the existence of a viable
TDE Qt4 theme engine alone--who knows what will happen now that Webkit and
other libraries are suddenly available for use in TDE!
Tim
I updated the bug tracker.
Anything related to building/compiling is now marked with the prefix 'Build issue: '. I modified the priority of a few. Most build issues are now tagged with Blocker, Critical, or Major, although there are other build issues rated lower.
Possibly I missed a few. Please check your own reports and add the 'Build issue: ' prefix as necessary.
With these updates, we now know which bug reports are build issues. Just search for 'Build issue: '. No need for an etherpad. :)
A check box would be nice. Does bugzilla support that?
http://bugs.pearsoncomputing.net/bugzilla/bugzilla/bugzilla/buglist.cgi?qui…
How many? 72 reports of build issues. Yet remember that many reports are similar --- resolve one report and resolve several.
Not necessarily related to build issues, there are 30 bug reports with attached patches. If we seek a way to triage the bug tracker, I recommend first focusing on Blocker reports, then Critical, then Major, etc., but within each priority, first address those with patches.
http://bugs.pearsoncomputing.net/bugzilla/bugzilla/bugzilla/bugzilla/buglis…
I will push patches to GIT but often I need technical review and approval. Sometimes one person is sufficient but other times more when I believe a "root cause analysis" is required, such as reverting patches. As project leader, Tim is an exception and when he says push I'll push.
Tim,
Unless I can do this on my own, would you please add my email address to the bug tracker notification list? That way I'll know about new bug reports and can quickly tag any new report as a build issue if needed. I then can post to this list any such new reports.
Darrell
When reviewing the source code, sometimes I see Qt:: prefixed and sometimes TQt::.
Which is correct? If both are correct then how does one determine appropriate context for each?
Thanks.
Darrell
All,
I have recently finished a initial conversion of kpowersave to work
without HAL, instead relying on the brand-new TDE hardware library, which
in turn works straight off of the raw device nodes in /sysfs.
As this is the last remaining large HAL dependency in TDE, I would
encourage the TDE developers to compile and test on their hardware,
reporting bugs to this mailing list.
The source code is available here:
http://git.trinitydesktop.org/cgit/kpowersave-nohal/
and can be obtained via:
git clone http://scm.trinitydesktop.org/scm/git/kpowersave-nohal
If this works reliably, along with the udev-based media kioslave:/, I will
seriously consider removing the TDE HAL dependency completely for R14.0.
Tim
In tdebase/kicker/data/kickoff, are image files that need branding updates:
kmenu_active.png
kmenu_basic.mng
kmenu_flipped.mng
kmenu_vertical.mng
I updated kmenu_active.png (GIT hash d4e6607ad6a9bfc49f4dfeced379c136704714b1), but the other three are animated (MNG) files that I can't perform mere touch up with kolourpaint. To my knowledge no TDE apps support MNG editing (viewing yes, editing no).
The only app I find for that is GIMP and I won't go there.
Would somebody with some MNG skills look at updating those three MNG images?
To update the logo, you should be able to grab the same from the kmenu_active.png I uploaded to GIT.
Thank you !
Darrell
Yesterday I patched many modules with various amounts of inadvertent "TQ" conversions. Most of them were harmless because the compiler doesn't know how to spell and the inadvertent changes were consistently mispelled.
Thus the packages compiled normally. The sources merely looked weird when reading the code. For example, ETQUAL vs. EQUAL, RETQUIRED vs. REQUIRED, UNITQUE vs. UNIQUE, etc.
The main reason for this cleanup effort is to restore the correct "human readability" of the source code.
However, a handful of the inadvertent conversions might have played a role in various bug reports. Might have.
If you have a favorite pet peeve bug then please rebuild from scratch in GIT and test again. No promises.
I suspect very few bugs will be resolved by this effort, but who knows? I now can see SVG images in the file preview tooltip in Konqueror as well as through the embedded viewer. I would appreciate confirmation from others with this bug (bug report 615).
Darrell
