All,
As some of you may already know, I have recently completed a large project
to reactivate Network Manager support on TDE. The new support is part of
tdelibs, and provides a fully abstracted interface that any TDE
application can use to read and/or change network settings and states
(depending on user permissions of course!). While the only backend
currently available was written to interface with NetworkManager, other
backends could be written in the future, allowing existing application
code to leverage multiple networking management platforms.
Additionally, I have ported the old knetworkmanager application to the new
API, and significantly cleaned it up along the way. The code for this new
application is available here:
http://git.trinitydesktop.org/cgit/knetworkmanager9/
Try it out and see what you think! As always, if you like it donations
are always welcome. ;-)
Tim
Hi all,
some time ago I announced that I'm prepare draft for update scripts for
work with Git. Now is attached both diff and tarball. I expect comments,
objections, other suggestions :)
Adjustments are as follows:
+ added support for branches
- the current branch is detected automatically
+ added automatic detection gituser (from .git/config)
+ optimized some operations
- if is not a mess, reset + clean is not called
- if there is nothing to commit, commit is not called
- if there is nothing to send server, push is not called
- because git submodule init + update in one call update all submodules,
for each git tree is called only once
I was thinking about add into script commit_all_submodules check for
untracked files. In order to avoid omission of renamed and new files.
What is your opinion?
Slavek
--
I asked this question many months ago, over on the 'users' list but
never got an answer, so here goes;
How do I get postgres support compiled into amarok (assuming said
support hasn't been removed) when building from the latest GIT source,
which uses cmake? There don't appear to be any clues in the
CMakeLists.txt files.
In the good old days it was as simple as '--enable-postgres'. Of course,
I could be missing something obvious :)
Cheers,
Mike.
--
Any question is easy if you know the answer!
In the latest Trinity news release:
The Trinity development team has adopted a "release when ready" approach but tentatively are focused on releasing R14.0.0 in the fall of 2012.
What is the definition of fall of 2012? Meteorological fall is ~September 21 to ~December 21. Traditional fall is September to November.
Do we have a release plan at all?
Darrell
What is a good way to address xsession log spew? Many messages are helpful for debugging, but under normal usage clutters the xsession log.
The messages should be toggled by the user as needed. Some examples:
[tdeinit] Got EXEC_NEW....
[tdeinit] PID xxxx terminated.
[tdeinit] Got SETENV....
[tdeinit] xxxx is executable and not a library. Launching with exec.
When I look at these messages in kinit.cpp I notice they are fprintf(stderr) messages and many are conditional, based upon #ifndef NDEBUG. Is NDEBUG a compile-time variable (meaning "No debug"), or is this variable configurable during run-time as an environment variable?
What options exist to reduce this spew?
Darrell
While tinkering with kdDebug I noticed the following message in my xsession log:
KDE4 is running
Um, nope, that would be incorrect. :)
The message is found in tdelibs/kded/kded.cpp:165-171:
TQString version = getenv( "KDE_SESSION_VERSION" );
TQStringList blacklist;
if ( version >= "4" )
{
kdDebug(7020) << "KDE4 is running." << endl;
blacklist << "mediamanager" << "medianotifier" << "kmilod" << "kwrited";
}
I'm no C++ coder but I believe the problem is 'version' is declared as a string but the test for the message is comparing a string to an integer. If I understand correctly, any non-zero value is treated as true. If KDE_SESSION_VERSION is empty then that value is not zero but null, which is a non-zero value?
Possibly the comparison test should change to:
if ( version != "" )
The KDE_SESSION_VERSION environment variable was introduced in KDE4 and did not exist in KDE3:
http://techbase.kde.org/KDE_System_Administration/Environment_Variables#KDE…
KDE_SESSION_VERSION will be set to some value only on a KDE4/5/6 system. Otherwise the getenv function returns null/empty. All we need determine is whether the variable is set to some value.
Comments?
Darrell
Hi all.
I have a suggestion to set default global shortcuts in kmix to
XF86AudioRaiseVolume, XF86AudioLowerVolume and XF86AudioMute. With this
settings should work immediately keys on multimedia keyboards.
Does anyone have any objections?
Slavek
--
When I run kdebugdialog to enable a single option, the result is that kdebugdialog creates a user kdebugdialogrc file with every option enabled.
Seems to me that the resulting kdebugdialogrc file should be the same as the system default with the only difference being the single change.
Would somebody please confirm this behavior?
Darrell
The summer season (in the northern hemisphere), traditionally a time when many people shift paces to enjoy outdoor activities and traveling, begins to close. Despite this traditional change of pace the past three months, Trinity development continued at a methodical pace. From June 1 to August 31 there were 131 bug reports or enhancement requests resolved in the bug tracker (http://bugs.trinitydesktop.org/bugzilla/buglist.cgi?bug_status=RESOLVED&chf…), as well as issues resolved through discussion in the developer's mailing list.
During the past several months, many changes occurred in the upstream free/libre software world, such as changes to GCC, GLIBC, GLIB2, LIBPNG, FFMPEG, HAL, etc. Those changes occurred in rapid succession and close proximity. Resolving Trinity related issues has been challenging.
The Trinity development team kept pace. The online Patches web page shows the progress of resolving those challenges: http://www.trinitydesktop.org/patches/
As autumn knocks on the doors of life, Trinity development continues:
* The 3.5.13.1 SRU (Stable Release Update) is only a few patches away from being released with official tarballs.
* A slew of TDEHWLIB updates were committed to the GIT development branch. TDEHWLIB is the eventual Trinity hardware detection layer replacement for HAL, and is already able to fully replace HAL in most areas.
* Network-manager improvements were committed to the GIT development branch.
* Koffice, K3B, and Gwenview i18n sources were committed to the GIT development branch.
* The R14 development branch was overhauled with XDG compliance updates. Trinity is now a recognized XDG environment.
* Comprehensive branding overhaul.
The Trinity development team has adopted a "release when ready" approach but tentatively are focused on releasing R14.0.0 in the fall of 2012. Also, the previously mentioned LDAP/Kerberos tools remain available in the TDE bounty program, with more information available on the TDE RFE page (http://www.trinitydesktop.org/crfe/#finished).
The Trinity development team hopes you enjoyed your summer. Soon in the northern hemisphere the leaves will turn color and in the southern hemisphere, leaves will sprout. Please enjoy the seasonal changes and thank you for being a member of this community!
--The Trinity News Team
