Re: ActiveTcl unbundling

On Dec 22, 5:46 am, Colin Macleod <colin.macl...@xxxxxxxxx> wrote:
On 22 Dec, 07:02, marc spitzer <ms4...@xxxxxxxxxxxxxxxxxxxxx> wrote:

Colin,

Perhaps you could just change your view a bit, just download everthing
and submit one itemized list for approval? after all even MS installs
have several cab files in them.

Unfortunately it's not my view that counts. The policy where I work
is strict and there's not much chance of influencing it. Even
updating one existing package to a new version needs a separate
approval, and justification in terms of what project it's needed for.
If ActiveTcl is no longer one well-defined package but a collection of
downloads the approval process will become very much harder.

Colin, I understand exactly what you mean. In my case, downloading is
a mess because no user has the ability to do this, and we have 1100+
machines - who wants, as an admin, to log into 1100 Windows machines
to run the commands? Plus, who wants the 1100 machines tied to one
shared folder (or server), so that when that machine goes down, they
all go down.

Note that there is, technically, one teacup package that you could
list as downloading to get what used to be Activetcl - it is the
package ActiveState::ActiveTcl . That package results in all the rest
of the dependencies being downloaded. But the local distribution is
still a problem.



A secondary issue is that the machines where I mostly use it do not
have direct internet access, so any download-on-demand system is not
workable there anyway.

Yep - that's my situation at home. I suppose you could, in theory,
download it all on one machine, put it onto a CD, then carry it home
and load it in the same place on the home machine.

Well, from Jeff's remarks, things probably will get better with 8.5.1
(or 8.6 - which ever it is called next).

.

Relevant Pages