There is some nominal support in kcontrol to support startup management.
I don't know what all is available in this area for KDE 3.5.x, but I'd like to see more.
As Slackers tend to be rather anal about such GUI apps <roll eyes>, very little in that way ever apeared in Slackware.
There is some kind of Lilo manager hook in kcontrol. There is something called qgrubeditor that supports GRUB 1. That tool now only supports QT4 (what's new). I don't see qgrubeditor in svn so here is a vote to support that.
Then there are the startup services and daemons. I don't know if any KDE GUI tool exists for that. If there I would appreciate a link so I can consider how that tool might be adapted to Slackware. I think the Ubuntu folks have something like that, but of course, GTK.
This all would be something for 3.5.13 of course.
Darrell
There is some nominal support in kcontrol to support startup management.
I don't know what all is available in this area for KDE 3.5.x, but I'd like to see more.
As Slackers tend to be rather anal about such GUI apps <roll eyes>, very little in that way ever apeared in Slackware.
There is some kind of Lilo manager hook in kcontrol. There is something called qgrubeditor that supports GRUB 1. That tool now only supports QT4 (what's new). I don't see qgrubeditor in svn so here is a vote to support that.
Then there are the startup services and daemons. I don't know if any KDE GUI tool exists for that. If there I would appreciate a link so I can consider how that tool might be adapted to Slackware. I think the Ubuntu folks have something like that, but of course, GTK.
This all would be something for 3.5.13 of course.
Darrell
Why don't you file a RFE bug at http://bugs.pearsoncomputing.net for that? I usually direct new developers to the bugtracker to fix items present there, as well as use it to prioritize development.
Thanks!
Tim
On Wednesday 15 September 2010 02:39:20 Darrell Anderson wrote:
[...]
Then there are the startup services and daemons. I don't know if any KDE GUI tool exists for that. If there I would appreciate a link so I can consider how that tool might be adapted to Slackware. I think the Ubuntu folks have something like that, but of course, GTK.
These things are very distro-dependent, I'm not sure that is good ideea to include it in KDE (maybe for this reason was not developed never this kind of support).
Becase we are only few developers (for now), maybe is better to focus to improve/fix already existent features. For example, kmail (or more exactly, kio_imap4) have a very annoying (and really old) bug which hang checking emails if network connection broke (or the machine wakeup after suspend). Also, kopete have poor support for file transfer (at least yahoo protocol, even I was patch it heavily). And, of course, we need to improve tqtinterface to support Qt4. There are a lot to do until we must thinking to develop something new :)
And my very science fiction ideea is to build an interface which will permit to compile KDE4 applications against trinity (a sort of compatibility layer) :)
On Wednesday 15 September 2010 02:39:20 Darrell Anderson wrote:
[...]
Then there are the startup services and daemons. I don't know if any KDE GUI tool exists for that. If there I would appreciate a link so I can consider how that tool might be adapted to Slackware. I think the Ubuntu folks have something like that, but of course, GTK.
These things are very distro-dependent, I'm not sure that is good ideea to include it in KDE (maybe for this reason was not developed never this kind of support).
Becase we are only few developers (for now), maybe is better to focus to improve/fix already existent features. For example, kmail (or more exactly, kio_imap4) have a very annoying (and really old) bug which hang checking emails if network connection broke (or the machine wakeup after suspend). Also, kopete have poor support for file transfer (at least yahoo protocol, even I was patch it heavily). And, of course, we need to improve tqtinterface to support Qt4. There are a lot to do until we must thinking to develop something new :)
And my very science fiction ideea is to build an interface which will permit to compile KDE4 applications against trinity (a sort of compatibility layer) :)
-- Serghei
Agree 100%. The only thing I would add is that every now and then the Trinity project gets some "green" developers that need a relatively simple task or tasks to get used to the development process. As a kcontrol module can be very simple (a UI file and some simple C++) this might be a good RFE for them to cut their teeth on. Hence my request to add it to the bugtracker. ;-)
After 3.5.12 is out we will need to get a list of future improvements and associated priorities together. The top two as far as I am concerned are: 1. Converting to the CMake build system (automake is getting long in the tooth and new, weird build problems seem to crop up for every release). 2 Adding Qt4 support to the TQt interface.
I cannot do either one by myself as they would take years when my other responsibilities are factored in. ;-)
Tim
For now I would at least like to see 1) the KControl Lilo editor supported and 2) the qgrubeditor added to Trinity.
While reading the responses I just remembered a KDE app called KSysV. That app is part of the kdeadmin package. Perhaps then managing startup services and daemons might not be that huge of a challenge.
To my knowledge KSysV does not work with BSD style init scripts, but should work with most other distros. The tool needs some polish. If some developers join the team perhaps they can look at adding that polish and even modifying or forking the tool for BSD style startup scripts.
Just thinking out loud. :)
For now I would at least like to see 1) the KControl Lilo editor supported and 2) the qgrubeditor added to Trinity.
While reading the responses I just remembered a KDE app called KSysV. That app is part of the kdeadmin package. Perhaps then managing startup services and daemons might not be that huge of a challenge.
To my knowledge KSysV does not work with BSD style init scripts, but should work with most other distros. The tool needs some polish. If some developers join the team perhaps they can look at adding that polish and even modifying or forking the tool for BSD style startup scripts.
<snip>
That would be a good starting point.
Also note that certain distributions may not even be able to do what is requested. For example Upstart, which is the "new" Ubuntu SysV replacement as of a couple releases ago, does not support the disabling of any startup services as of Lucid. (!).
Tim
On Wednesday 15 September 2010 04:27:48 Timothy Pearson wrote:
[...]
After 3.5.12 is out we will need to get a list of future improvements and associated priorities together. The top two as far as I am concerned are:
- Converting to the CMake build system (automake is getting long in the
tooth and new, weird build problems seem to crop up for every release).
I working hard on this :) The migration to cmake is pretty easy (thanks to kde3 support builtin in cmake), but need a lot of work.
I estimate that in few weeks will be done migration for kdelibs.