From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Subject: Re: [ITP] mtr
Date: Mon, 22 Jul 2019 11:36:00 -0000 [thread overview]
Message-ID: <99772313-ada0-8180-08b0-e94589f925db@dronecode.org.uk> (raw)
In-Reply-To: <e9cb61fb-0314-b04f-36ec-e2cf17e7a284@SystematicSw.ab.ca>
On 21/07/2019 19:27, Brian Inglis wrote:
> On 2019-07-21 12:10, Brian Inglis wrote:
>> On 2019-07-21 06:59, Jon Turney wrote:
>>>
>>> Not sure what you intend, so either (i) explicitly configure --without-gtk, or
>>> (ii) add the needed gtk devel package(s) to DEPENDS.
My fractured grammar probably didn't help make clear that I consider
either of these alternatives valid.
From what you write, it seems you really intended to omit gtk support,
so I'd suggest you consider alternative (i) i.e. explicitly configure
--without-gtk, and potentially revisit this when someone demonstrates a
need for mtr with gtk.
> 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 guess you could add a mtr-gtk subpackage, to contain a mtr built with
gtk support.
Unfortunately cygport can't create subpackages with conflicting files,
and we can't mark packages as conflicting (yet), so you'd need to rename
the mtr executable in that subpackage (e.g. as mtr-gtk)
next prev parent reply other threads:[~2019-07-22 11:36 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 [this message]
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
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=99772313-ada0-8180-08b0-e94589f925db@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--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).