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

List:       kde-edu
Subject:    Re: [kde-edu]: Starting work in KDE4
From:       Jason Harris <kstars () 30doradus ! org>
Date:       2006-04-22 19:23:29
Message-ID: 444A82B1.1000606 () 30doradus ! org
[Download RAW message or body]

I do it the same way as Carsten now, after messing around with one user 
for a while.  The only annoyance for me is that I edit the code using 
KDevelop executed as my "jharris" user, but the files reside in the 
"kde-devel" user's directory.  So when I run "svn up", any modified 
files are no longer writable by jharris (so I have to "chmod g+w" them 
as kde-devel).

Actually, this is easily solved by the builddir != srcdir setup required 
by cmake.  I can just keep the source code under /home/jharris, and keep 
the builddir under /home/kde-devel...problem solved.

Jason

Carsten Niehaus wrote:
> This is my way:
> 
> I have two users: "carsten" and "kde4". Of course, all kde4-related things
> are done as "kde4". I log in as carsten but "su - kde4" to that user and
> start coding. I have my XOrg configured in a way that the user kde4 can run
> a x-app in 'carsten's xserver (xhost + for example does the job).
> In 'kde4's .bashrc I export things like QTDIR. I have kdelibs_snapshot,
> kdebase, kdeedu and qt-copy, all from /trunk/ checked out for that user
> (including commit-rights).
> 
> ./kalzium starts a kde4-Kalzium on the xserver without any problems...
> 
> Doing the same with only one useraccount is *much much* harder... My setup
> takes only about 5 minutes to set up (plus compiling qt+kde, of course).
> 
> Carsten
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> kde-edu mailing list
> kde-edu@mail.kde.org
> https://mail.kde.org/mailman/listinfo/kde-edu

_______________________________________________
kde-edu mailing list
kde-edu@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-edu
[prev in list] [next in list] [prev in thread] [next in thread]