From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31770 invoked by alias); 30 Sep 2017 13:14:56 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 31382 invoked by uid 89); 30 Sep 2017 13:14:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=preferably, Indeed, H*M:c0ac, enjoy X-HELO: mout.gmx.net Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.17.22) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 30 Sep 2017 13:14:54 +0000 Received: from [192.168.15.105] ([92.20.186.130]) by mail.gmx.com (mrgmx101 [212.227.17.174]) with ESMTPSA (Nemesis) id 0Mecqq-1divVz1EoC-00OGJa for ; Sat, 30 Sep 2017 15:14:51 +0200 Subject: Re: Dependency issues in setup.ini. To: cygwin@cygwin.com References: <505405e4-5a2f-8d6b-f012-404bd7d69009@gmx.com> <216159991.20170930120008@yandex.ru> <171d601b-59c2-f186-5213-12c6b6f493cd@gmx.com> <19010162357.20170930142314@yandex.ru> From: Sam Edge Message-ID: Date: Sat, 30 Sep 2017 13:28:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <19010162357.20170930142314@yandex.ru> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-UI-Out-Filterresults: notjunk:1;V01:K0:9QfoP8fa3WQ=:9614LArNRAEqVNg1BiihVO Vs8uzLVG/jBgJO+rehIPfMv1ssWF6h+76Q3Msm7e5BXDzFhEr3xyE8mC4iF+syudf9d+rt5pv qvoepI6VwdI8ApiFu+G1ZtTS6O0kjYSD49oJtif3iSHdAnaucmzttr2ZR7N9oRmGYGqnNuxd3 l0KopWtBso7z5zYn5HfC5Qr1VH5PSk0AfVrBREHhb+xYcBAqNtUMjYL6T05aVfFW2T1jmGMfO wiVwDdh4spfvN9a+MKiBYdqyJ9fb+bgG1C23yKTs1Z21K19pLEpAjugGMYPt1f8MMZGrjT/DR 9fXTZXdpFru0JKE+QrsLCMH2YTFGoVD+xkbLajT8p2JCg0hYj/6OBnJ+vQV73N9dAfoy5BgVe P7JqHMW8vNY333lw2X9ETiDGjybQvqVFs6E/RQSbr2sKcZvyaXuoj8DlBwdShfNdlU7/3Tr8M CbuegTo4+j0TEUnmQKX2r8iffa9dkY2LFTx1u9Xn5fIFw+3A4G7CPEkgaUIn1bvo0AD6CzRD5 PciGiHbtlhxu4ooP+b9/bhXzI79KcDtZtlcg1Ag2p/fo825ydRAeRwclavVsmx1Kc8j0TQYCh w8CGjtVYYKo8/IjV/YijtpIiok/dvyCw8D+dVS3201/8SPFS/AX2777/hLa05ixqSUCPZjpkl cX9toQtNYesWL5A8jwuilrBHXGWMCJosVse7It7Oavo7ZPzD/+7UcN+k7MrjS14Cl6evqjw+9 395QWy5rIDgNpbyWATOYf9BKGGvU0SC2Oz2dJc58uNgxrV/43Iq/+bNiWqWohGczbTEvNEzhQ bJOA+gz4+rAiRlpS9J8XW9Sjg2JWvvdrUErWxyaYNCHTwdMFSM= X-IsSubscribed: yes X-SW-Source: 2017-09/txt/msg00315.txt.bz2 On 30/09/2017 12:23, Andrey Repin wrote: > >> Indeed. However, while off label usage of Cygwin is anathema to me but >> sometimes I wish 'base' wasn't quite so big and have to pare things down >> a little once installed, e.g. as part of a makefile- and/or >> Eclipse-based build tree in source code control.(Which was also one of >> my motivations for the Python stuff.) > Rational suggestions are always welcome, I suppose. > While my own usage of Cygwin is prone to spread thin across all aspects of my > daily work, I can see situations, where a much smaller subset of packages > (let's name it "core" or something) would be beneficial. I.e. when packaging > Cygwin as part of your own application. > > Again, agree. A 'core' package that has enough to get a shell up (preferably dash not bash) would be very useful. I don't believe in packaging Cygwin with an application - I'd rather say "as a prerequisite, you need to have a Cygwin installation newer than v.X" - but for build systems where you're trying (somewhat in vain sometimes I know) to attempt deterministic behaviour it would be nice to have a smaller subset upon which you could add just what's needed, usually make, grep, sed, cp, mv & rm & maybe a scripter such as awk, perl, tcl (or python!) depending upon. Anyway, it's the weekend so I'm off. Enjoy, -- Sam -- 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