From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6 v2] package/libgtk2: break a circular dependency
Date: Sun, 7 Feb 2016 00:02:05 +0100 [thread overview]
Message-ID: <20160207000205.2699d7e9@free-electrons.com> (raw)
In-Reply-To: <20160206225310.GB3429@free.fr>
Dear Yann E. MORIN,
On Sat, 6 Feb 2016 23:53:10 +0100, Yann E. MORIN wrote:
> I have absolutely no preference between the two.
There is indeed a subjective decision to be made here. But I believe
it's better to loose some relatively useless GUI programs, rather than
the some printing support in a GUI library.
> The only I'm tangentially interested in is the cups -> avahi
> dependency.
Fully agreed that keeping this dependency is important, and the most
important on of the chain.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-06 23:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 16:02 [Buildroot] [pull request v2] Detect and fix circular dependencies Yann E. MORIN
2016-01-24 16:02 ` [Buildroot] [PATCH 1/6 v2] package/libgtk2: break a circular dependency Yann E. MORIN
2016-02-06 22:46 ` Thomas Petazzoni
2016-02-06 22:53 ` Yann E. MORIN
2016-02-06 23:02 ` Thomas Petazzoni [this message]
2016-01-24 16:02 ` [Buildroot] [PATCH 2/6 v2] package/libgtk3: " Yann E. MORIN
2016-01-24 16:02 ` [Buildroot] [PATCH 3/6 v2] support/graph-depends: detect circular dependencies Yann E. MORIN
2016-01-24 16:02 ` [Buildroot] [PATCH 4/6 v2] support/graph-depends: add option to specify output file Yann E. MORIN
2016-02-06 23:00 ` Thomas Petazzoni
2016-01-24 16:02 ` [Buildroot] [PATCH 5/6 v2] support/graph-depends: teach it to only check dependencies Yann E. MORIN
2016-01-24 16:02 ` [Buildroot] [PATCH 6/6 v2] core: add a make target to check the dependencies Yann E. MORIN
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=20160207000205.2699d7e9@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.