From: "Matt Seitz (matseitz)" <matseitz@cisco.com>
To: <cygwin@cygwin.com>
Subject: Re: gitk fails to start after updating cygwin
Date: Mon, 27 Feb 2012 19:35:00 -0000 [thread overview]
Message-ID: <70952A932255A2489522275A628B97C31294EF95@xmb-sjc-233.amer.cisco.com> (raw)
"Yaakov (Cygwin/X)" wrote:
>
> Remember that using X requires some level of manual intervention,
namely
> that you have to *start* the server and set DISPLAY before actually
> using it.
> So installing xorg-server as a dependency isn't going to
> prevent these questions one bit.
Good point. Would adding "xinit" as a dependency be a better solution?
I am hoping that when "setup" informs the user that "gitk requires
xinit", it might it at least:
1. Alert the user to the fact that gitk now requires loading the X
server.
2. Spare the user having to run "setup" again to download the packages
they need.
--
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 reply other threads:[~2012-02-27 18:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 19:35 Matt Seitz (matseitz) [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-24 22:43 Matt Seitz (matseitz)
2012-02-24 22:54 ` Larry Hall (Cygwin)
2012-02-24 23:38 ` Mike Kaganski
2012-02-25 4:42 ` Larry Hall (Cygwin)
2012-02-26 4:36 ` Yaakov (Cygwin/X)
2012-02-24 20:50 Matt Seitz (matseitz)
2012-02-24 22:16 ` Larry Hall (Cygwin)
2012-02-24 19:26 Matt Seitz (matseitz)
2012-02-24 20:09 ` Corinna Vinschen
2012-02-10 23:41 Matt Seitz (matseitz)
2012-02-10 23:02 Arnon Moscona
2012-02-11 5:40 ` marco atzeri
2012-02-17 22:34 ` Bill Hoffman
2012-02-17 22:55 ` marco atzeri
2012-02-21 2:32 ` Yaakov (Cygwin/X)
2012-02-20 8:34 ` Csaba Raduly
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=70952A932255A2489522275A628B97C31294EF95@xmb-sjc-233.amer.cisco.com \
--to=matseitz@cisco.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).