> setup.exe uses the 'requires: ' statement to implement dependency checking. > See the setup.ini format at the above referenced URL. > > - between Cygwin packages, > > - between a package and cygwin.dll.
Does setup.exe support uninstalling just like rpm -e package name does? Are dependencies taken into account during uninstall? > The cygwin1.dll is in the 'cygwin' pacakge. Anything that depends on the > cygwin1.dll can optionally list the cygwin package. However setup will > install everything in base regardless (unless overridden), so the cygwin > package is an optional requirement. Is Cygwin listed in each package dependency? > The cygIPC package is deliberately not included in the cygwin distribution > (see the cygwin-apps archive for the reasons). Any other package will > install all it's dependencies automatically. OK then. If I only want ot install PostgreSQL, it will only download the required dependencies, right? Does the installer check version dependency? > What cygwin allows is a matter of policy, the same as for debian. Setup.exe > is perfectly capable of installing native windows packages. I did not know that. This is very interesting. > Why do you say setup.exe is horrible? Bad architecture? Bad GUI? Doesn't > work? The last two days of MD5 related errors that I have not had time to > look at? Bad GUI for sure. 1) There should be a small descrition of each package like in .DEB or .RPM packages. A single line is not enought. A Windows user does not know what he is downloading. 2) Packages should be listed in an on-line database. With a full description and manuals. 3) Cygwin installer should be accessible in the Control Panel directly or in Add/Remove software. Presenty, it can only be access through the setup.exe 4) We need a setup.exe command line tool to implement limited installers that will not conflict with setup.exe. Example : if we release a limited Cygwin installer at PostgreSQL, we need to be sure it will not conflict with Cygwin. What is the on-going work as for setup.exe? Could you describe shortly what is in the hub ? Cheers, Jean-Michel POURE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
