From: Sam Edge <sam.edge@gmx.com>
To: cygwin@cygwin.com
Subject: Re: Dependency issues in setup.ini.
Date: Sat, 30 Sep 2017 13:28:00 -0000 [thread overview]
Message-ID: <c6a001dc-1940-cdfd-c0ac-144c6f697f5c@gmx.com> (raw)
In-Reply-To: <19010162357.20170930142314@yandex.ru>
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
next prev parent reply other threads:[~2017-09-30 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 22:39 Sam Edge (Cygwin)
2017-09-29 23:54 ` Steven Penny
2017-09-30 8:43 ` Sam Edge (Cygwin)
2017-09-30 9:05 ` Marco Atzeri
2017-09-30 2:34 ` Doug Henderson
2017-09-30 7:57 ` Steven Penny
2017-09-30 10:57 ` Andrey Repin
2017-09-30 11:35 ` Sam Edge
2017-09-30 11:51 ` Andrey Repin
2017-09-30 13:28 ` Sam Edge [this message]
2017-10-02 13:25 ` Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c6a001dc-1940-cdfd-c0ac-144c6f697f5c@gmx.com \
--to=sam.edge@gmx.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).