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

List:       kde-edu
Subject:    Re: [kde-edu]: Starting work in KDE4
From:       Andreas Nicolai <Andreas.Nicolai () gmx ! net>
Date:       2006-04-23 15:13:36
Message-ID: 200604231150.39568.Andreas.Nicolai () gmx ! net
[Download RAW message or body]

Hi,

thanks for the suggestions. QT4 is compiling right now (and probably for the 
next 2 hours :-)

> 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).

Here the umask command may help. You can set the new file creation mask to 
something that your other developer user can read+write, so for simplicity, 
you could use umask in your bashrc as:

umask g=rwx

and thus all your files created (e.g. by KDevelop) will get a rw flag for the 
users group, which the kde4 user belongs to as well. 


Andreas


_______________________________________________
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]