Seems a fine start. Can you post it on the wiki?
Do we have a check list to help developers/packagers watch for QA problems with packages? I have not seen any. How about we start one?
1. Check two apps in each menu category of the T-Menu to verify the Help file handbook is available.
2. Run a system test looking for broken sym links. (I use a short script I can share.)
3. Do all apps in the T-Menu start?
4. Check the xsession logs for unexpected or unusual errors and messages.
5. Do kdesu/kdesudo work as expected for your distro?
This is just for starters. Please add to this list.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting