Date: Tue, 04 Sep 2001 02:52:53 -0500 From: Jim Bryant <kc5vdj@yahoo.com> To: "Brian T.Schellenberger" <bts@babbleon.org> Cc: Martti Kuparinen <martti.kuparinen@iki.fi>, will@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: ports/30294: Can't unlock KDE Message-ID: <3B948855.9090703@yahoo.com> References: <20010904091704.O27939-100000@server.nomadiclab.com> <01090403430201.19266@i8k.babbleon.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, there seems to be one change that I have noticed in this version of KDE. KDE itself won't block you from using xlock, as in
the previous version. Just create a link on the desktop to xlock.
Brian T.Schellenberger wrote:
> On Tuesday 04 September 2001 02:20, Martti Kuparinen wrote:
>
>>On Mon, 3 Sep 2001 will@FreeBSD.org wrote:
>>
>>>It's not setuid root for security reasons. See x11/kdebase2/pkg-message.
>>>
>>Ok, but if one performs "make install" in x11/kde2 like I did,
>>this message will be "lost" in the dependency build phase. Maybe
>>this should be displayed at the end of x11/kde2 as well?
>>
>
> In general, somehow gathering up "critical messages" might be a nice feature
> for ports.
>
> In this case, the default results from the install are (IMHO) particularly
> useless, though, so perhaps instead of it just being a pkg-message, the port
> could actually stop and prompt the user for a decision about whether or not
> to chmod or, at least prompt him to acknowledge that he saw the message?
>
>
>>Martti
jim
--
ET has one helluva sense of humor!
He's always anal-probing right-wing schizos!
--------------------------------------------
POWER TO THE PEOPLE!
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B948855.9090703>