Ulli Horlacher writes: >> You have to install Cygwin, not "transfer". > > I have several 100 users, none of them is able to install cygwin and > the packages they need the official way, they are way to *CENSORED* for > this job :-}
If they can follow your current instructions, they can surely start some script that does this correctly? > I give them my preconfigured cygwin.zip (or cygwin64.zip) and tell them to > unpack it in C:\ > > http://fex.belwue.de/usecases/cygwin.html > > (This is what I call "transfer cygwin") Whatever you call it, it's still cludgey nonsense that might or might not work. Only when it's not working your users will really be unable to figure out what to do since they won't even know what is failing. Again, to provide your tools properly for Cygwin, create a Cygwin package, set up a package repository that provides it and then start a script that calls setup to install it and any other packages you need (if not already installed by way of dependency). Setup can deal with multiple package repositories, so you can use one of the official mirrors as the primary package repository and only provide your package as an add-on repository (like cygwin ports does). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
