Hi again, I am running a ubuntu dapper under vmware for testing and package compilation.
I was playing around with revision .3.1 for sometime and understand there are quite a number of changes in initscripts and base with revision .4 What would you suggest, as a best practise, to see the changes made since revision 3.1 ? As the sources are quite componentized i am not sure on the best approach here. I would be comforable to run a directory+file visual Diff to see the changes between two revisions. But for that which package sources should i download for checking? What would be the best practice here? As i am running dapper, should i create a special account (openthinclient, otc) and use chroot for the base? Just curious how the developers working approach is for updates to the base and other packages. Do i need to create the OTC (or whichever its called in the compiled version) account and do a chroot? Would appreciate your detailed reply very much as I would like to get my hands dirty (add printer drivers, do some quick fixes) but i dont know the best practices used by the developers. thank you in advance. Cheers! -- View this message in context: http://www.nabble.com/Best-Practise-to-understate-the-code-changes-between-revisions-tp21734955p21734955.html Sent from the openthinclient.org users' mailing list mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ The Open Source Thin Client Solution http://openthinclient.org [email protected] https://lists.sourceforge.net/lists/listinfo/openthinclient-user
