From: Adrian Bunk <bunk@stusta.de>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/7] libgnomekbd: cleanup DEPENDS inherit gsettings / remove unused config
Date: Sun, 1 Dec 2019 19:35:01 +0200 [thread overview]
Message-ID: <20191201173501.GJ4526@localhost> (raw)
In-Reply-To: <20191201165123.12699-1-schnitzeltony@gmail.com>
On Sun, Dec 01, 2019 at 05:51:17PM +0100, Andreas Müller wrote:
> * DEPENDS: ... gtk+3 pulls glib-2.0
>...
> -DEPENDS = "gconf glib-2.0 libxklavier gtk+3 intltool-native"
> +DEPENDS = "gtk+3 libxklavier"
>...
It is better to have explicit dependencies on everything used directly
by the recipe.
gtk+3 -> glib-2.0 is not a dependency that is likely to go away in the
future, but in general relying on indirect dependencies tends to break
frequently.
cu
Adrian
next prev parent reply other threads:[~2019-12-01 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 16:51 [PATCH 1/7] libgnomekbd: cleanup DEPENDS inherit gsettings / remove unused config Andreas Müller
2019-12-01 16:51 ` [PATCH 2/7] gnome-system-monitor: add gsettings to inherit Andreas Müller
2019-12-01 16:51 ` [PATCH 3/7] tracker-miners: initial add 2.3.1 Andreas Müller
2019-12-01 16:51 ` [PATCH 4/7] nautilus: add tracker-miners to RDPENDS Andreas Müller
2019-12-01 16:51 ` [PATCH 5/7] xserver-xorg-cvt-native: initial add 1.20.5 Andreas Müller
2019-12-02 6:28 ` Khem Raj
2019-12-01 16:51 ` [PATCH 6/7] mutter: initial add 3.34.1 Andreas Müller
2019-12-01 16:51 ` [PATCH 7/7] nodejs: Add PACKAGECONFIG share to allow other projects to use node as library Andreas Müller
2019-12-01 18:52 ` Khem Raj
2019-12-01 17:35 ` Adrian Bunk [this message]
2019-12-01 18:50 ` [PATCH 1/7] libgnomekbd: cleanup DEPENDS inherit gsettings / remove unused config Khem Raj
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=20191201173501.GJ4526@localhost \
--to=bunk@stusta.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=schnitzeltony@gmail.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 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.