From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6 v2] package/libgtk2: break a circular dependency
Date: Sat, 6 Feb 2016 23:53:10 +0100 [thread overview]
Message-ID: <20160206225310.GB3429@free.fr> (raw)
In-Reply-To: <20160206234634.37caec35@free-electrons.com>
Thomas, All,
On 2016-02-06 23:46 +0100, Thomas Petazzoni spake thusly:
> On Sun, 24 Jan 2016 17:02:36 +0100, Yann E. MORIN wrote:
> > We currently have a circular dependency chain:
> >
> > avahi -> libglade -> libgtk2 -> cups -> avahi
> >
> > The cups -> avahi dependency makes sense, as cups would be able to use
> > Bonjour and mDNS to find printers, so we want to keep that dependency.
> >
> > The avahi -> libglade -> libgtk2 chain also makes some sense, to provide
> > a GUI frontend for avahi.
> >
> > Since the libgtk2 -> cups does not look that it would be tremendously
> > useful, that's the one we drop in this patch.
>
> I tend to disagree with this analysis. The avahi GUI programs seem
> really useless to me. On Debian/Ubuntu distributions, they are not even
> packaged within the main avahi packages, but as separate packages,
> probably indicating that they are not very commonly used. It is also
> highly unlikely that such ready-made applications will be used on
> embedded systems.
>
> On the other hand, when you enable Gtk2 or Gtk3 to create your
> own graphical applications, you may be interested in being able to have
> the print dialogs support CUPS.
>
> So in the:
>
> avahi -> libglade -> libgtk2 -> cups -> avahi
>
> I would rather tend to break the dependency between "avahi -> libglade"
> rather than between "libgtk2 -> cups".
>
> (This comment obviously also applies to your patch 2/6).
>
> What do you think ? What do others think ?
I have absolutely no preference between the two. The only I'm
tangentially interested in is the cups -> avahi dependency.
So I'm fine with your proposal as well.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-02-06 22:53 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 [this message]
2016-02-06 23:02 ` Thomas Petazzoni
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=20160206225310.GB3429@free.fr \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox