This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: setup
- From: Warren Young <wyml at etr-usa dot com>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 10 Aug 2015 10:45:16 -0600
- Subject: Re: setup
- Authentication-results: sourceware.org; auth=none
- References: <87vbcwfdvw dot fsf at Rainer dot invalid> <87r3nkfaxn dot fsf at Rainer dot invalid> <87mvy8f8dz dot fsf at Rainer dot invalid> <20150803202908 dot GI17917 at calimero dot vinschen dot de> <87a8u8f4s5 dot fsf at Rainer dot invalid> <871tfidhrm dot fsf at Rainer dot invalid> <20150805080833 dot GT17917 at calimero dot vinschen dot de> <87614tn3nm dot fsf at Rainer dot invalid> <20150806100338 dot GY17917 at calimero dot vinschen dot de> <87d1z0if40 dot fsf at Rainer dot invalid> <20150807194737 dot GO12475 at calimero dot vinschen dot de> <874mkawe0c dot fsf at Rainer dot invalid> <FA0668B5-C99E-49AD-9947-28DBD595A06B at etr-usa dot com> <87tws7rtb2 dot fsf at Rainer dot invalid>
On Aug 10, 2015, at 10:40 AM, Achim Gratz wrote:
>
> Warren Young writes:
>
>> In that sense, setup.exe is already bootstrapped: it has everything
>> within itself to be able to replace itself.
>
> I do like the concept of a self-contained executable, but teaching
> setup.exe new tricks is likely a larger effort than adding a script here
> and there to an install system.
Isnât the whole point of this discussion that setup.exe already knows all the tricks it needs to in order to do what we want here, except for the âreplace setup.exe in placeâ issue Iâve brought up separately?
Why do you need a self-contained POSIX environment to replace setup.exe?