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 08:44:29 -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>
On Aug 7, 2015, at 11:22 PM, Achim Gratz <Stromeko@nexgo.de> wrote:
>
> a minimal Cygwin install system w/ busybox
Busybox isnât going to be usable in its normal sense without cygwin1.dll to map symlinks to argv[0] so that Busybox can tell how it was called, and thus which function to provide.
But thatâs a side issue, because I donât see why you think you need Busybox in the first place, unless it is to be able to run postinst scripts. Canât you just say that that setup-*.tar.xz package never has a postinst script, so that all you need to do is un-tar it?
In that sense, setup.exe is already bootstrapped: it has everything within itself to be able to replace itself.