> 
>  >. That brings up a couple of issues.
>  >>
>  >> 1. Do I need to do something about my $HOME/.teapot about this, or is
> 
>  >> that all taken care of?
> 
>  >I am not clear if I understand the question correctly.
>  >What do you believe should be done ?
>  >I am certainly not touching it with the new installation, no change, no
>  removal.
> 
>  I had somehow missed the part of the release announcement about moving
>  away from the old default. This question is no longer relevant. Thanks!

You are welcome.


> 
>  >> 2. What do I need to do to convince teacup that the install is okay -
> 
>  >> that the repository at that directory ... which has solaris 2.8 sparc
> 
>  >> binaries in it right now ... is okay?
>  >>
>  >> Or, am I using the --arch flag wrong?
> 
>  >What does
>  >	teacup link info /vol/tclsrcsol/ActiveTcl-8.5.1/lib/teapot
>  >	say ?
> 
>  $ teacup link info /vol/tclsrcsol/ActiveTcl-8.5.1/lib/teapot
>  Shell /vol/tclsrcsol/ActiveTcl-8.5.1/bin/tclsh8.5

Ok.

>  Shell /projects/sprs_lwv/tcl85/bin/tclsh8.5

Where is this one coming from ? I am guessing that this shell was made known
by an explicit 'link make' on your part.

>   $ /vol/tclsrcsol/ActiveTcl-8.5.1/bin/tclsh8.5
>  % package require platform
>  1.0.3
>  % platform::identify
>  solaris2.9-sparc
> 
>  However, solaris2.9-sparc isn't one of the options in teapot at this
>  time...

If you say '--arch solaris2.9-sparc' it should take the solaris2.8 packages,
as they are compatible. It should even do so even if you are not specifying
arch at all.


>  The whole reason I was adding the --arch was so that I didn't replicate
>  the problem I had previously, where my attempt at installing some code
>  via teacup caused both solaris2.6-sparc and solaris2.8-sparc versions to
>  be installed. So being the "clever" person, I thought "oh, I'll just
>  specify the specific platform I want and that will take care of my
>  concerns.

The issue of taking both 2.8 and 2.6 is a problem in the 'update' command,
'install' should not have that issue.

If you have an older teacup it may pull the solaris2.6 instance over the
solaris2.8 instance, however I corrected that recently (last monday, it was
an issue of sort-order, buildno 284067). The latter means that this should
not be an issue for you, as I remember that you run 'teacup update-self'
quite often.

> 
>  Apparently, tcl is more clever than I am...

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

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