From: Henning <xaoxx@t-online.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] mtr
Date: Mon, 22 Jul 2019 13:42:00 -0000 [thread overview]
Message-ID: <e57250c5-3d1f-a4ab-99a3-1a2e8afe2ece@t-online.de> (raw)
In-Reply-To: <e9cb61fb-0314-b04f-36ec-e2cf17e7a284@SystematicSw.ab.ca>
On 21/07/2019 20:27, Brian Inglis wrote:
> Built with gtk2.0-devel installed now requires libgdk_pixbuf2.0_0 libglib2.0_0
> libgtk2.0_0 which probably drags a lot of X in.
> Is there a standard way to offer subpackages with and without X in these cases?
I usually do what I can to avoid X stuff. If I can afford it I decide to
not install packages. In this case I would probably try to compile
myself.
Henning
next prev parent reply other threads:[~2019-07-22 13:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 23:15 Brian Inglis
2019-07-21 12:59 ` Jon Turney
2019-07-21 18:10 ` Brian Inglis
2019-07-21 18:27 ` Brian Inglis
2019-07-22 11:36 ` Jon Turney
2019-07-23 12:03 ` Brian Inglis
2019-07-23 13:37 ` Henning
2019-07-24 12:25 ` Brian Inglis
2019-07-24 13:59 ` Henning
2019-07-22 13:42 ` Henning [this message]
2019-07-23 12:04 ` Brian Inglis
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=e57250c5-3d1f-a4ab-99a3-1a2e8afe2ece@t-online.de \
--to=xaoxx@t-online.de \
--cc=cygwin-apps@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).