AlphaWiki/CVS/CVS Updates Alphatk Windows

Note: this page needs more work. At present it is not much more than a mirror of CVS.AlphaTclCvsOldVersion.

This page contains information for updating from the AlphaTcl CVS for Alphatk in the Windows OS.

Important Note (15 May 2006) : http://sourceforge.net/ has announced a change in its CVS servers, and the Server Hostname should no longer be

 
   cvs.alphatcl.sourceforge.net
    cvs.sourceforge.net

but rather

 
   alphatcl.cvs.sourceforge.net

Note: currently Alphatk assumes an encoding for AlphaTcl that is fixed in the distribution you downloaded (could be cp1252, macRoman or other -- look in alphatk.tcl). However, the repository is latin1 encoded (or for Tcl's purposes ISOmacRoman encoded), so appropriate conversion steps will be needed after checkouts/updates; this requirement will go away in the near future, or if you install the ISOmacRoman encoding and have Alphatk use that. (the appropriate .enc file for tcl based conversion is provided in Developer/Tools/encoding)

Setup

CLI Instructions (csh assumed)

It is suggested you place the following in your ~/.cvsrc :

 
   cvs -z3
   diff -u
   update -P -d
   checkout -P

For users and developers with read-only pserver access:

initial checkout (use an empty password at prompt)

 
	setenv CVSROOT ':pserver:anonymous@alphatcl.cvs.sourceforge.net:/cvsroot/alphatcl'
	cvs login

subsequent cvs operations in AlphaTcl $HOME won't need any setup as a toplevel CVS directory is created.

For members of the AlphaTcl SF project with read-write access:

setup ssh so that you can login to cvs.sourceforge.net and add the following to your ~/.cshrc : (not sure this is needed, it might be set by default by SF)

 
	setenv CVS_RSH ssh

initial checkout (replace developername by your SF username)

 
	setenv CVSROOT ':ext:developername@alphatcl.cvs.sourceforge.net:/cvsroot/alphatcl'

subsequent cvs operations in AlphaTcl $HOME won't need any setup as a toplevel CVS directory is created.
If you want to hide the new CVS directories (in your filesets, for instance), you can simply enter 'CVS' as the file pattern to ignore in the various edit-filesets dialogs.
note that if running on Windows under cygwin, I'm not sure if the above will work or not. I've found that typing 'export CVS_RSH=ssh' does the trick. That's a shell issue, the above is for csh derivates, if you're using a sh derivate such as bash (the default on the SF shell server and many Linuces), replace 'setenv A B' by 'export A=B'
NOTE: if you have never used sourceforge cvs via ssh before for any SF project, your will probably also need to login to the commandline host alphatcl.sourceforge.net with an ssh client and your SF username and password; once logged in, type 'ssh cvs1' on the commandline there. This will login to the cvs server, create a home directory on the cvs server, and logout immediately. This procedure only needs to be done _once_ per SF user account. (c.f. [http://sourceforge.net/docman/display_doc.php?docid=765&group_id=1])

Checkout, Update

The repository is designed to be checked out in your Alpha directory, i.e. the AlphaTcl $HOME.

CLI Instructions (csh assumed)

To checkout execute the following in AlphaTcl $HOME:

Developers

 
	cvs co -A -r CURRENT AlphaTclDevel

Users

 
	cvs co -A -r STABLE AlphaTcl

To update, execute the following in AlphaTcl $HOME

 
	cvs up *

(ignore the warning about 'CVS' being specified in the argument)

Developers could use '-r HEAD' to get the absolute latest version of everything in the repository, but that will be less stable, and much more likely to have bugs.

Alphatk extra instructions

Download Alphatk and follow the above instructions (CLI) to get a working checkout of AlphaTcl. You will notice that Alphatk already contains an AlphaTcl distribution. Replace that distribution with the checked-out version (containing 'CVS' directories etc). Be careful not to delete any part of the hierarchy (AlphaCore, AlphaGifs, for example) which is not included in the checked-out copy.

Now edit 'alphatk.tcl' and change the default encoding to 'ISOmacRoman' (search for the string "macRoman"). You need to do this because you've just replaced a 'macRoman' encoded AlphaTcl with an 'ISOmacRoman' one. Now start up Alphatk as usual. There may be some issues wrt your preferences being in the wrong encoding.

Once you have this setup up and running, you can update AlphaTcl in place. Updates to the non-AlphaTcl parts of Alphatk must still be done by downloading an Alphatk distribution.

Category.CVS