All,
I have cannibalized a systemd service file from kde for use with tde. It is as
basic as it can be. Is there anything else anybody can think of that we need to
do with the tdm.service file for tdebase?
--
David C. Rankin, J.D.,P.E.
> I recall a protracted discussion about whether to show the
>shutdown dialog
>with all of the options or just logout. IIRC out of that
>discussion the
>following patch was born 'tdebase-feedbackdlg.diff' I cannot find
>where it is
>applied in the code. Do you recall what happened to this issue?
KControl->TDE Components->Session Manager->Show logout status dialog
Darrell
> In working tdebase patches, I note that one of the traditional
>patch files to
I don't know what you mean by traditional patch files.
If you are still applying patches from years ago, then likely you
will make a mess. :)
The only patches I apply these days are patches in the queue from
the bugzilla or patches I create for testing. There are no more
traditional patch files. Those days are long gone.
Check the git history for patches:
http://git.trinitydesktop.org/cgit/
You can narrow your search to specific cpp files.
If you find no evidence a patch was applied --- and that includes
remembering to check against all of the renaming and rebranding,
then check the bugzilla. There remain many open bug reports with
patches that have not been merged into git.
When you check the bugzilla remember to use the ALL keyword to
search closed and resolved reports too.
If you come up empty, then file a new report and attach the patch,
updated for renaming.
Darrell
Darrell,
I recall a protracted discussion about whether to show the shutdown dialog
with all of the options or just logout. IIRC out of that discussion the
following patch was born 'tdebase-feedbackdlg.diff' I cannot find where it is
applied in the code. Do you recall what happened to this issue?
--
David C. Rankin, J.D.,P.E.
Tim, Darrell,
In working tdebase patches, I note that one of the traditional patch files to
the kdebase source (existing in patches.tar.bz2 -
08-kip_kdesktop_rounded_icon_text_corners.patch) is not applied in the current
git source, and fails to apply due to the file name change. I think it is
probably a good idea to keep the patch. The patch is:
diff -Naur kdebase-3.5.8.orig/kdesktop/kfileividesktop.cpp
kdebase-3.5.8/kdesktop/kfileividesktop.cpp
--- kdebase-3.5.8.orig/kdesktop/kfileividesktop.cpp 2007-10-08
15:58:03.000000000 +0200
+++ kdesktop/kfileividesktop.cpp 2007-11-20 13:57:09.000000000 +0100
@@ -100,6 +100,13 @@
// draw the pixmap as in KIconViewItem::paintItem(...)
paintPixmap(p, colors);
+ if ( isSelected() ) {
+ p->setBrush( TQBrush( cg.highlight() ) );
+ p->setPen( TQPen( cg.highlight() ) );
+ p->drawRoundRect( textRect( FALSE ),
+ 1000 / textRect( FALSE ).width(),
+ 1000 / textRect( FALSE ).height() );
+ }
My question is did all the code class names change as well?? I guess it
doesn't matter here, but I've grepped and the only thing I come up with is:
tdefileividesktop.cpp:87:void KFileIVIDesktop::paintItem( TQPainter *p, const
TQColorGroup &cg)
So I think the comment above is wrong as well. Do we want to try and apply the
traditional KDE patches that remain in patches.tar.bz2 to the code before R14
release (fix them once and for all)? the only patches that remain are:
patches/08-kip_kdesktop_rounded_icon_text_corners.patch
patches/03-kcontrol_advbg_step.patch
patches/06-nspluginscan-xdgcompliance.patch
patches/01-kicker-lockout-applet-button-order.patch
Let me know. I'll keep tweaking these for now.
--
David C. Rankin, J.D.,P.E.
Darrell, Tim, All,
Job well done. I've build tde through tdelibs on bleeding-edge arch without
issue (ok - well giant PITA rearranging dependencies, inventing systemd services
files, etc. -- but NO TDE CODE issues)
The current dependency and packages successfully built are:
apetag-git-1.13-1-x86_64.pkg.tar.xz
libkarma-0.1.2-1-x86_64.pkg.tar.xz
libnjb-2.2.7-3-x86_64.pkg.tar.xz
libutempter-1.1.6-2-x86_64.pkg.tar.xz
mt-daapd-0.2.4.2-7-x86_64.pkg.tar.xz
musepack-tools-svn-r484-1-x86_64.pkg.tar.xz
tde-arts-14.0.0-1-x86_64.pkg.tar.xz
tde-avahi-tqt-14.0.0-1-x86_64.pkg.tar.xz
tde-dbus-1-tqt-14.0.0-1-x86_64.pkg.tar.xz
tde-dbus-tqt-14.0.0-1-x86_64.pkg.tar.xz
tde-libart-lgpl-14.0.0-1-x86_64.pkg.tar.xz
tde-libcaldav-14.0.0-1-x86_64.pkg.tar.xz
tde-libcarddav-14.0.0-1-x86_64.pkg.tar.xz
tde-python-tqt-14.0.0-1-x86_64.pkg.tar.xz
tde-sip-14.0.0-1-x86_64.pkg.tar.xz
tde-sip4-tqt-14.0.0-1-x86_64.pkg.tar.xz
tde-tdelibs-14.0.0-1-x86_64.pkg.tar.xz
tde-tqca-tls-14.0.0-1-x86_64.pkg.tar.xz
** I split tqt3 into 2 packages **
tde-tqt3-14.0.0-1-x86_64.pkg.tar.xz
tde-tqt3-docs-14.0.0-1-x86_64.pkg.tar.xz
tde-tqtinterface-14.0.0-1-x86_64.pkg.tar.xz
wv2-0.4.2-3-x86_64.pkg.tar.xz
xmedcon-0.13.0-1-x86_64.pkg.tar.xz
tdebase builds TONIGHT!
--
David C. Rankin, J.D.,P.E.
> If you have konversation installed, just run it, the first
>screen pops up and
>tells you which channel is the default. You can cancel then.
Okay, thanks.
Incredibly, the defaults are hard-coded rather than as part of a ui
file or default rc file.
applications/konversation/konversation/src/config/preferences.cpp:72
-79
serverGroup->setName("Ubuntu IRC");
server.setHost("irc.ubuntu.com");
channel.setName("#kubuntu");
Is the following correct to patch the defaults for Trinity?
serverGroup->setName("Trinity IRC");
server.setHost("irc.freenode.net");
channel.setName("#trinity-desktop");
Darrell
>Only way to check is to fire it up and see if you have an active
>connection to
>kde. We should really change it to open #trinity-desktop on
>freenode :-)
I don't do IRC. If I did I would not have asked the question. :)
Darrell
All,
I don't use konversation.
The following is a konversation What's This popup:
"When Konversation is started for the first time, the Freenode
network and the <i>#kde</i> channel are already entered for you."
The po files repeat the same text.
Is that statement true?
Darrell
>Grrr. I knew I missed out of something important. I'm still
>putting everything
>in /opt/tde and all my packages are tde-appname-ver-minver.tar.xz.
>At least
>changing the prefix= will be a snap, picking through the build &
>conf files may
>be a bit of fun ;-)
I don't know that /opt/tde won't work. I haven't tried.
The 'trinity' tag was agreed upon for package names.
Using /opt/trinity would make your builds consistent with the
package names. Also, the default profile directory is ~/.trinity,
therefore /opt/trinity would match that too.
Consistency tends to makes us bipeds warm and fuzzy. :)
If you have a working copy of tdewebdev installed, even 3.5.x, give
tdefilereplace a whirl. Fairly slick tool for performing multi-line
search and replace operations. I've used the tool several times to
perform mass updates of my build scripts.
Darrell