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

List:       kde-core-devel
Subject:    Re: Can we please have an updated and confirmed working "build KDE
From:       Mark <markg85 () gmail ! com>
Date:       2012-01-02 16:59:02
Message-ID: CAPd6JnFssN4HxFnG=XwkAzVZ=j4K7AwxVEeh3KnkAxbUnH3yKw () mail ! gmail ! com
[Download RAW message or body]

On Mon, Jan 2, 2012 at 12:59 AM, Shaun Reich <shaun.reich@kdemail.net>wrote:

> Honestly, running a separate user for it just makes everything more a
> pain than it should be.The better way is to just run it under your
> user but use different environment variables when you want to run
> master apps. Your crash is likely caused by the fact that you
> attempted to run an application (Dolphin) from master, yet it was
> still using the $QTDIR from /usr/.., in other words probably too old.
>
> I just have a command, "runmaster" which switches the current shell to
> one that has all the environment vars setup to run a compiled
> application. This way I can have a stable desktop, and run and test
> things from master manually and whenever I want to.
>
>
> Actually, yes, I see that your QTDIR is pointing to /usr. That is
> incorrect for building from source.
>
> Truly, I recommend not going the separate user route, that's sort of
> why it's not well documented. Mostly because it shouldn't be used..in
> fact, I even added it somewhere a long time ago saying that other
> methods are better than a separate user (no idea if it's there or not,
> some people go too crazy on wiki edits and don't preserve enough past
> info).
>
> That is completely the opposite of what was suggested to me in the last
few months of the kde svn days. Back then it was specifically suggested to
use a separate user for kde developing stuff. Don't know who suggested it.

I personally like to have it all as a separate user since then everything
is just at one place and i can test it as if i had the latest kde version.
either way, having your script would probably help a lot. Can you put it on
techbase?

[Attachment #3 (text/html)]

<div class="gmail_quote">On Mon, Jan 2, 2012 at 12:59 AM, Shaun Reich <span \
dir="ltr">&lt;<a href="mailto:shaun.reich@kdemail.net">shaun.reich@kdemail.net</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">

Honestly, running a separate user for it just makes everything more a<br>
pain than it should be.The better way is to just run it under your<br>
user but use different environment variables when you want to run<br>
master apps. Your crash is likely caused by the fact that you<br>
attempted to run an application (Dolphin) from master, yet it was<br>
still using the $QTDIR from /usr/.., in other words probably too old.<br>
<br>
I just have a command, &quot;runmaster&quot; which switches the current shell to<br>
one that has all the environment vars setup to run a compiled<br>
application. This way I can have a stable desktop, and run and test<br>
things from master manually and whenever I want to.<br>
<br>
<br>
Actually, yes, I see that your QTDIR is pointing to /usr. That is<br>
incorrect for building from source.<br>
<br>
Truly, I recommend not going the separate user route, that&#39;s sort of<br>
why it&#39;s not well documented. Mostly because it shouldn&#39;t be used..in<br>
fact, I even added it somewhere a long time ago saying that other<br>
methods are better than a separate user (no idea if it&#39;s there or not,<br>
some people go too crazy on wiki edits and don&#39;t preserve enough past<br>
info).<br><br></blockquote><div>That is completely the opposite of what was suggested \
to me in the last few months of the kde svn days. Back then it was specifically \
suggested to use a separate user for kde developing stuff. Don&#39;t know who \
suggested it.</div>

<div><br></div><div>I personally like to have it all as a separate user since then \
everything is just at one place and i can test it as if i had the latest kde \
version.</div><div>either way, having your script would probably help a lot. Can you \
put it on techbase?</div>

</div><br>



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