I always rebuild from scratch. Starting from tqt3 and working down. I have
a build script that lets me press the button and go away for a couple of
hours ... hopefully without error.
BTW: I am building everything to /usr with no sign of KDE4. So far the base
(that i need) builds nicely ... just a few niggling runtime errors.
Jay
On Sat, Apr 28, 2012 at 4:28 PM, Darrell Anderson
<humanreadable(a)yahoo.com>wrote;wrote:
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. :-)
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting