A single alternate ActiveState install package would be handy. This way,
there would be the current one for development, and a "run-time" package,
for distribution only. This run-time could be identical to the current
package, minus the PythonWin IDE, and the Python Docs.
Of course, I could create my own, but hoping for an ActiveState one solves
two problems:
1) Not having to update the package with each Python rev, and ...
2) Avoiding the effort myself (true, lazy!).
I have found that the .MSI package from ActiveState works quite well. I just
have not made the journey to create one from scratch.
-----Original Message-----
From: steve [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 29, 2000 7:30 AM
To: Echeverria Rabi, Cristian Rodrigo, TRANSELEC S.A.
Cc: [EMAIL PROTECTED]
Subject: Re: ActivePython Win32 Installer Subset
Outside of any wierd keys that may be loaded into the registry(some dumb
companies do this to FORCE a monopoly), you can try just about any
installer.
The trick is getting ALL of the right dlls. Even activestate could have
problems with this. Sadly, python isn't popular enough to likely have its
own
setup in WISE, etc... At one point, even VB suffered this fate(and it still
does sometimes between versions), and people just hacked it. Heck, I
generall
use the freeman installer which has NO base setups!
BTW, MANY installers have a configuration file, or can use one as a basis,
so
writting a whole new installer would be silly.
Steve
"Echeverria Rabi, Cristian Rodrigo, TRANSELEC S.A." wrote:
_______________________________________________
ActivePython mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/activepython
