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

List:       kde-core-devel
Subject:    Re: Potential problems for developers (LONG) ignore if you are happy with the status quo
From:       Jason Stephenson <panda () mis ! net>
Date:       2001-03-31 19:24:44
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If I understood the question correctly, it was basically, "How do you develop 
the current version of KDE and use it and test it, and still keep the last 
stable KDE around for everyday use, or for emergency use when something is 
FUBAR in the currect CVS?"

What I did when the work for KDE 2 was going on and KDE 1.1.2 was the stable 
release was to have two user accounts. My regular user account ran the stable 
KDE, but the environment for user kde2test was set up to run the KDE2 
compiled from CVS.

What I am going to do next is have two scripts to start KDE. One sets up the 
environment for the last stable release and the other sets up the environment 
for KDE from CVS, which is in /home/$USER/kde. I plan to also have separate 
.kde (for stable) and .kde2 directories, or at least have the script for KDE 
from CVS backup the current .kde directory in case something gets FUBAR.

Does that answer your question?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjrGLwYACgkQRZu1ZcECWs0aYQCfSe3u+2CgCeqDQYbqEzkR01Kx
iaMAoMd60nI+1T9wfA9asZTw/CJ8kRGA
=c1uo
-----END PGP SIGNATURE-----

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