> One quick question: How does one determine which "r" version (r348, > r387, etc.) of cluebringer one has installed?
Either using subversion cli or the web interface I guess. If you do a "svn info", it will show you what revision you have. http://svn.linuxrulz.org/WebSVN/listing.php?repname=Cluebringer&path=%2Ftags%2F&rev=0&sc=0 Click on one of the tags, and check "Last Modification". I think this should be relatively correct to use. You need to run all the upgrading commands when moving to v2.1. The revisions are there for v2.1.x updates so you can ignore them moving to v2.1 from v2.0. While I try be as accurate as possible, please just try it on a test platform first :) . If you use trunk by doing your own checkouts the revision is displayed after each update. Would be a good idea to check the revision before and after an update and watch for any changes to the UPGRADING file. This is when you need to run commands and pay attention to the revision numbers. An example of planned changes is one major change in future relating to the naming of MessageCount , it will change to RecipientCount and MessageCount be redefined as how many messages are transmitted regardless of the number of recipients. This is when paying attention to the UPGRADING file will be vital :) -N
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
