So, today I was working on making the new activetcl 8.5 available on one
of my solaris machines.

However, the first thing that hit me was that I need to maintain two
local repositories. I need one that will stay nearly static, and
I will need one where I will test new packages. Once the package has
been tested, and someone decides that it is suitable for production,
I then need to install that particular version into the nearly static
repository.

So, I used
   * ./teacup create to create a new repository,
   * ./teacup link to break the connection from the default repository, as well
	as to indicate to teacup that the new tclsh had its own repository
   * ./teacup default to point to the new repository
   * ./teacup install ActiveState::ActiveTcl to install the latest 
	set of commonly used packages.

At this point I ran into the first weirdness. teacup displays a lot of output
then tells me that the items were already installed, followed by a message
saying some dependencies couldn't be resolved.

So, I decided to try

   * ./teacup install --dry-run --force --with-recommends ActiveState::ActiveTcl

expecting this command to show me what it was doing, so Instead, after pages
of output, I get a long string of "Installing package" messages. So I'm
running that now, to see if it will populate the new repository.

Does this sound like I'm headed down the right path? Are there any other
gotchas to keep in mind while managing multiple local repositories?
-- 
Tcl - The glue of a new generation.  <URL: http://wiki.tcl.tk/ > 
Larry W. Virden <mailto:lvirden@[...].org> <URL: http://www.purl.org/NET/lvirden/ >
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-> <-
_______________________________________________
ActiveTcl mailing list
ActiveTcl@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs