Message: previous - next
Month: April 2012

Re: [trinity-devel] kcmshell keys

From: Darrell Anderson <humanreadable@...>
Date: Sat, 28 Apr 2012 12:28:41 -0700 (PDT)
> Thanks for testing. I am using git from around 1 week ago. Will pull latest and
> retest. Havn't had much time for testing during last month but back into it now.

When testing with GIT builds often I uninstall all previous packages. Clean house. Cleaning house means looking for orphaned files, such as scripts in etc/profile.d. Then I rebuild my complete set again starting with TQt3. Right now I build almost everything to /opt/trinity. When I perform a full uninstall I end up with no /opt/trinity directory --- nominal evidence of a good uninstall.

When I 'git pull' tdebase I always check tdelibs too. If tdelibs has changed then I rebuild that module before building tdebase to continue testing. Those two modules go hand-in-hand.

Being methodical like this is somewhat a PITA, but I seem to avoid problems. GIT is too much of a moving target and rebuilding everything every several days seems saner for me in the long run. :-)