This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: AdminCygwin Release
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: BGINFO4X <bginfo4x at kztsoftware dot com>, cygwin at cygwin dot com
- Date: Thu, 23 Jan 2014 20:06:05 +0400
- Subject: Re: AdminCygwin Release
- Authentication-results: sourceware.org; auth=none
- References: <CAO2ddnbtJ_mY1Yei6cx2GQO1dAWv=OV-cDVFO+aZD935MGQ7mA at mail dot gmail dot com> <52DEBB76 dot 2040004 at cygwin dot com> <CAO2ddnb+Vfn+199r-qqmPF=tL5XeEmYO2Qmn+=d2sKw4QK2Ong at mail dot gmail dot com>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, BGINFO4X!
>> not the least of which is that it will be a burden for you to keep up-to-date.
> I will not try to keep up-to-date. Only "major releases" will produce
> a new .msi. Upgrades should be done via "apt-cyg".
apt-cyg is NOT a supported way of updating Cygwin installation.
setup*.exe is.
As Larry Hall pointed out, if you want a normal, non-ambiguous way to provide
your product within Cygwin environment, you have to create a package and
distribute it through Cygwin mirrors.
If you want an installer THAT bad, make an installer, that download architecture-
appropriate setup*.exe and launch it with selected commandline options to
install required packages.
--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 23.01.2014, <19:57>
Sorry for my terrible english...
--
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