On Feb 2 23:24, Jon TURNEY wrote:
Make a copy of setup.exe as /bin/cygwin-setup.exe.
This enables a few useful things:
- Register that copy of setup.exe with Add/Remove programs
While that sounds nice, doesn't that introduce more puzzled questions?
I can easily imagine people thinking they
2011/2/3 Corinna Vinschen:
On Feb 2 23:24, Jon TURNEY wrote:
Make a copy of setup.exe as /bin/cygwin-setup.exe.
This enables a few useful things:
- Register that copy of setup.exe with Add/Remove programs
Shouldn't we start to seperate pure mingw executables from cygwin somewhen?
Then we
On 2/3/2011 8:13 AM, Reini Urban wrote:
2011/2/3 Corinna Vinschen:
On Feb 2 23:24, Jon TURNEY wrote:
Make a copy of setup.exe as /bin/cygwin-setup.exe.
This enables a few useful things:
- Register that copy of setup.exe with Add/Remove programs
Shouldn't we start to seperate pure mingw
On Wed, Feb 02, 2011 at 11:24:58PM +, Jon TURNEY wrote:
Make a copy of setup.exe as /bin/cygwin-setup.exe.
This enables a few useful things:
- Register that copy of setup.exe with Add/Remove programs
- Add a start menu item pointing to that copy of setup.exe
- Type 'cygwin-setup -q -Ppackage'
On Thu, Feb 3, 2011 at 8:53 PM, Christopher Faylor wrote:
On Wed, Feb 02, 2011 at 11:24:58PM +, Jon TURNEY wrote:
Make a copy of setup.exe as /bin/cygwin-setup.exe.
This enables a few useful things:
- Register that copy of setup.exe with Add/Remove programs
- Add a start menu item pointing
2011/2/3 Charles Wilson:
On 2/3/2011 8:13 AM, Reini Urban wrote:
2011/2/3 Corinna Vinschen:
On Feb 2 23:24, Jon TURNEY wrote:
Make a copy of setup.exe as /bin/cygwin-setup.exe.
This enables a few useful things:
- Register that copy of setup.exe with Add/Remove programs
Shouldn't we start
