On Mon, Sep 13, 2004 at 08:54:11PM +0200, Jan Nieuwenhuizen wrote: >Igor Pechtchanski writes: > >> Not really. As Max said, the environment in which the postinstall scripts >> run is the same as the one you'd get when you run them on the command line >> (albeit from a non-login /bin/sh). That environment will contain all of >> the Windows-set environment variables. If the tools require that some >> variables be unset (because they might throw the tools off, for example), >> the variables have to be unset in the postinstall script -- setup.exe >> can't be expected to know all of the variables potentially conflicting >> with all of the packages. > >No, of course. That's why I'd like to have an empty (rather than a >cleaned) environment, isn't that possible? That sounds cleaner than >fixing all scripts?
No, you can't have a completely empty environment on Windows. There are some environment variables that really have to be there. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
