[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [PATCH] Re: resurrecting kwrited
From:       "George Kiagiadakis" <kiagiadakis.george () gmail ! com>
Date:       2008-10-20 14:39:36
Message-ID: ba4a6e220810200739jcd30040n4d7fa8f434e2d63a () mail ! gmail ! com
[Download RAW message or body]

2008/10/20, Oswald Buddenhagen <ossi@kde.org>:
> the utempter test is duplicated, which is just ugly.
>
>  i think the entire kwrited should be factored out from konsole - it is
>  there only for historical reasons. probably it should be kicked from
>  kdebase and moved to kdeutils or so.

I agree to that, but I am not sure what is the policy about moving
stuff. Can I "just do it" ? (I guess not...) Plus that we are in a
soft feature freeze...

>  > 1) The kwrited executable (if built as an executable) is setgid to the
>  > utmp group. I am not sure if all distros that do not ship libutempter
>  > use this group for /var/run/utmp and /var/log/wtmp. At least debian
>  > does.
>  >
>
> given that debian (+ derivatives) is probably the only distri not
>  shipping utempter ... :D
>  anyway, i think this group is fairly standard. if not, then somebody
>  will have to introduce a check and a variable to make it work on his
>  system.

Actually, I already noticed this is a problem on mac (it seems that
kwrited must be setuid root), although I didn't investigate it much. I
will figure this out (hopefully)...

>  > Also, I am unsure if the commands in that desktop
>  > file are correct (although they do work for me). This desktop file is
>  > supposed to be installed in ${AUTOSTART_INSTALL_DIR} to start kwrited
>  > by default on startup. The commands are somehow based on
>  > ${AUTOSTART_INSTALL_DIR}/krunner.desktop
>  >
>
> uhm ... no idea. does it work? :D

works fine :)
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]