Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] libsm: remove dependency on e2fsprogs
Date: Sun, 04 Jan 2015 10:09:56 +0100	[thread overview]
Message-ID: <54A90364.6060906@topic.nl> (raw)
In-Reply-To: <24dbafa66cc993d1b626ae27ea3e462c0af54718.1420337434.git.Qi.Chen@windriver.com>

On 01/04/2015 03:11 AM, Chen Qi wrote:
> This patch is to solve the following circular dependency problem.
>
>       systemd -> dbus -> libsm -> e2fsprogs -> util-linux -> systemd
>
> libsm doesn't have any dependency on e2fsprogs. It might be some dependency
> on util-linux's libuuid, controlled by configure options. So e2fsprogs should
> be removed from the DEPENDS variable.
>
> Ideally, we should add a PACKAGECONFIG for 'libuuid' for libsm. However, if
> libsm depends on util-linux, we would have the circular dependency described
> above. That's why this patch explicitly set '--without-libuuid' in EXTRA_OECONF.
> libsm would still be working well because it would fall back to an internal
> algorithm to do the uuid stuff.

Maybe libuuid should get its own recipe. It can be built from the 
util-linux sources. Other packages can then just depend on that libuuid 
recipe instead of util-linux itself.

Only problem would be util-linux I guess, you'd get two providers for 
libuuid.

-- 
Mike Looijmans


  reply	other threads:[~2015-01-04  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04  2:11 [PATCH 0/3] Upgrade util-linux and fix related circular dependencies Chen Qi
2015-01-04  2:11 ` [PATCH 1/3] util-linux: upgrade to 2.25.2 Chen Qi
2015-01-04  2:11 ` [PATCH 2/3] systemd: remove util-linux from DEPENDS Chen Qi
2015-01-04  2:11 ` [PATCH 3/3] libsm: remove dependency on e2fsprogs Chen Qi
2015-01-04  9:09   ` Mike Looijmans [this message]
2015-01-05  1:33     ` ChenQi
2015-01-19  1:36 ` [PATCH 0/3] Upgrade util-linux and fix related circular dependencies ChenQi

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=54A90364.6060906@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.org \
    /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