I like this solution very much!

On 4/26/06, Anthony Kozar <anthonykozar@sbcglobal.net> wrote:
> Rather than bug the user for not having Python installed, it seems better to
> me to simply provide checkboxes in the installer for optional components
> that have other dependencies.  This is what other installers do and it is an
> available feature in the standard Windows and Mac installers.
>
> So, a box for CsoundVST, a box for Python opcodes & interfaces, a box for
> TclCsound, etc.  The help messages for the optional checkboxes should
> explain what dependencies are required.  If the user checks a box that
> requires Python and they do not have it installed, then maybe they should be
> warned.
>
> On MacOS 9, I put all of the Python extras into a separate folder of the
> Csound 5 package.  That way the user can install them if they want them, but
> they will not see a "Failed to load library pylib" everytime they run Csound
> if they do not have Python installed.  I also usually test my packages on a
> "clean" machine to verify that end users will have the user experience I
> expect them to.
>
> Anthony Kozar
> anthonykozar AT sbcglobal DOT net
>
>
> Steven Yi wrote on 4/26/06 6:03 PM:
>
> > I think that the correct way to go about it would be for the installer
> > to check if Python exists on the host system, and if it does not
> > exist, offer a message to say "Python was not found on your system. To
> > use the Python opcodes and CsoundVST, please install now (Python
> > installer available from http://www.python.org) and press Retry, or
> > click cancel to continue on with installation.
>
> --
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>