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

List:       kde-devel
Subject:    Re: A few questions
From:       James Richard Tyrer <tyrerj () acm ! org>
Date:       2007-10-26 4:48:49
Message-ID: 472171B1.4050409 () acm ! org
[Download RAW message or body]

Andreas Pakulat wrote:
> On 03.10.07 19:12:32, James Richard Tyrer wrote:
>> Eligio Becerra Zavala wrote:
>>> Hello everybody
>>>
>>> I'm trying to become a KDE developer, and so far I've been able to 
>>> build KDE4 from SVN (following techbase howto), but I still have a 
>>> few questions about running and developing KDE4
>>>
>>> Which is the best way to develop on KDE4? Solitary session, Nested
>>> session? 
>> The best way to test something is to use a solitary session with a KDE4 
>> test user account.  Any other way and you run the risk of missing bugs. 
>>   This is very simple to do with KDE, just "Switch User :: Start New 
>> Session:.
>>
>> I have to say that the same is true of the method in the techbase howto. 
>>   If you install in: $HOME/kde rather than /usr/local/KDE-4.0. (note 
>> that "/local" is optional) you run the same risks.
> 
> Hmm, I agree with the "use fresh user" thing (although in that case you
> miss bugs that come up because you use existing configuration), but I
> can't imagine what bugs you can find by changing the installation
> directory to usr/locla/<something. In fact some months ago I found a few
> (buildsystem) bugs because I installed into $HOME/kde4/<module> (which
> takes quite more work to setup the env for though). - Just curious.
> 
The most common problem would be build system bugs where the build 
system is dependent on something being installed in a specific path.  It 
is possible for runtime bugs to appear for the same reason.

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