Our release candidates for the first release of a fattened up ActiveTcl 8.5
are now available at

	ftp://ftp.tcl.tk/pub/incoming/ActiveTcl8.5.3.0.286404-aix-rs6000-threaded.t
ar.gz
	ftp://ftp.tcl.tk/pub/incoming/ActiveTcl8.5.3.0.286404-hpux-parisc-threaded.
tar.gz
	ftp://ftp.tcl.tk/pub/incoming/ActiveTcl8.5.3.0.286404-html.tar.gz
	ftp://ftp.tcl.tk/pub/incoming/ActiveTcl8.5.3.0.286404-linux-ix86-threaded.t
ar.gz
	ftp://ftp.tcl.tk/pub/incoming/ActiveTcl8.5.3.0.286404-linux-x86_64-threaded
.tar.gz
	ftp://ftp.tcl.tk/pub/incoming/ActiveTcl8.5.3.0.286404-macosx-universal-thre
aded.dmg
	ftp://ftp.tcl.tk/pub/incoming/ActiveTcl8.5.3.0.286404-solaris-ix86-threaded
.tar.gz
	ftp://ftp.tcl.tk/pub/incoming/ActiveTcl8.5.3.0.286404-solaris-sparc-2.8-thr
eaded.tar.gz
	ftp://ftp.tcl.tk/pub/incoming/ActiveTcl8.5.3.0.286404-win32-ix86-threaded.e
xe

for testing by early adopters.

Notable changes:

	The distributions contain a TEApot repository preloaded with a number
	packages. This repository is installed under INSTALLDIR/lib/teapot.

	If a conflict is detected, for example by installing the new distribution
	into the same directory as a previous distribution new enough to have
	their TEApot repository in the same place, then the installer should
	ask the user on how to proceed and then act as chosen. Otherwise it
	should simply install the preloaded	repository in that location.

What we are now looking for are test users trying these distributions  and
reporting on their actual experiences with this mechanism in their
environment(s).

	I.e. is the conflict detection happening correctly ?

	Is the way the user can choose among the conflict resolution options ok ?

	Are the actions taken after the user has made his/her choice correct ?

	Etc.

>  Donald G Porter wrote:
>  > Jeff Hobbs wrote:
>  >> a. Use installing distribution repo (blow away pre-existing)
>  >> b. Use pre-existing repo (don't update with distro repo)
>  >> c. Merge
>  >
>  > Take my comments FWIW.  I've got little experience with ActiveTcl
>  > and none with teacup.  But I do know the capabilities of Tcl's
>  > [package] command.

>  The key aspect overlooked here is the need to maintain data consistency
>  in the local repo, which is a db file.
> 
>  > That ought to leave the options at two:  Install the bundled packages
>  > (merging them into the installed collection, that is, (c)), or don't

--
	Andreas Kupries <andreask@[...].com> 
	Developer @ http://www.ActiveState.com
	Tel: +1 778-786-1122


_______________________________________________
ActiveTcl-Dev mailing list
ActiveTcl-Dev@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs