public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Chris Wagner <wagnerc@plebeian.com>
To: cygwin@cygwin.com
Subject: Dependancy Hell (was Re: [ANNOUNCEMENT] Updated: mintty 2.9.9)
Date: Thu, 28 Mar 2019 18:22:00 -0000	[thread overview]
Message-ID: <1565df06c4b8f64bac8d5ab8c169904c@plebeian.com> (raw)
In-Reply-To: <5c9cb1c3.1c69fb81.d132f.62a6@mx.google.com>

On 2019-03-28 7:36 am, Steven Penny wrote:
> On Thu, 28 Mar 2019 08:34:34, Thomas Wolff wrote:
>> Mintty can be used to run any command-line application directly (like 
>> top, your editor, ...), a shell is not needed.
> 
> That may be true, the by default Mintty is configure to load Bash. So 
> it is
> disingenuous so simply say that it does not require a shell, unless you 
> want to
> change the default to load "top" as you said.
> 

I think that part of the issue is that there is no clear definition of a 
dependancy.  I encounter questionable dependancies all the time from 
Cygwin Setup.  If I try to install the wrong thing, there is a whole 
ecosystem of packages that come with it that I don't want.  I just don't 
install that thing I wanted and live without it or get it another way.

Likewise there are dependancies that are merely advisory and the package 
works just fine without it.

I think that a package should only be listed as a dependancy if the 
upstream package will not even run without it.  Things like library 
packages.  Even if it provides core functionality, if the main package 
will run, it's not a dependancy.  Dependancy hell is one of the few 
things I don't like about Cygwin.


Thanks.


--
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

  parent reply	other threads:[~2019-03-28 18:22 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-16  9:35 [ANNOUNCEMENT] Updated: mintty 2.9.9 Thomas Wolff
2019-03-16 14:01 ` Achim Gratz
2019-03-24 14:51   ` Steven Penny
2019-03-24 15:57   ` Thomas Wolff
2019-03-24 16:24     ` Brian Inglis
2019-03-24 18:19     ` Corinna Vinschen
2019-03-24 23:36       ` Thomas Wolff
2019-03-25  8:31         ` Corinna Vinschen
2019-03-25 18:12         ` Achim Gratz
2019-03-27 20:02           ` Thomas Wolff
2019-03-27 20:36             ` Achim Gratz
2019-03-27 21:01               ` Jeffrey Walton
2019-03-27 22:52             ` Steven Penny
2019-03-27 23:09               ` Yaakov Selkowitz
2019-03-28  1:12                 ` Steven Penny
2019-03-28  2:35                   ` Yaakov Selkowitz
2019-03-28  2:44                   ` Brian Inglis
2019-03-28  3:42                     ` Steven Penny
2019-03-28  7:34                       ` Thomas Wolff
2019-03-28 11:36                         ` Steven Penny
2019-03-28 15:09                           ` Brian Inglis
2019-03-28 18:22                           ` Chris Wagner [this message]
2019-03-28 17:37                         ` Achim Gratz
2019-03-27 22:59             ` Yaakov Selkowitz
2019-03-28  7:15               ` Björn Stabel
2019-03-28 17:40                 ` Achim Gratz
2019-03-28 18:08                   ` Thomas Wolff
2019-03-28 18:21                     ` Achim Gratz
2019-03-28 18:32                       ` Thomas Wolff
2019-03-28 19:47                         ` Achim Gratz
2019-03-28 21:38                           ` Thomas Wolff
2019-03-28  8:43               ` Thomas Wolff
2019-03-28  9:36                 ` Corinna Vinschen
2019-03-28 14:02                 ` Jeffrey Walton
2019-03-28 18:10                   ` Thomas Wolff
2019-03-28 18:16                     ` Vince Rice
2019-03-28 18:33                       ` Thomas Wolff
2019-03-28 18:43                         ` Vince Rice
2019-03-28 21:34                           ` Thomas Wolff
2019-03-28 22:28                             ` Steven Penny
2019-03-24 21:05     ` Andrey Repin

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=1565df06c4b8f64bac8d5ab8c169904c@plebeian.com \
    --to=wagnerc@plebeian.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).