From: Khem Raj <raj.khem@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: update-alternatives questions
Date: Sat, 21 Jan 2012 19:09:34 -0800 [thread overview]
Message-ID: <20120122030934.GE27997@sakrah.homelinux.org> (raw)
In-Reply-To: <55ACB0DC-90E8-4A61-89FC-D51A01B69FF2@dominion.thruhere.net>
On (17/01/12 10:07), Koen Kooi wrote:
>
> Op 17 jan. 2012, om 01:43 heeft Andreas Müller het volgende geschreven:
>
> > Hi
> >
> > when starting a fresh image (angstrom/opkg) I see for xfwm4 (xfce window manager
> > included in meta-oe)
> >
> > S98configure[285]: //var/lib/opkg/info/xfwm4.postinst: line 2: update-
> > alternatives: command not found
> >
> > I checked:
> >
> > * there is no update-alternatives in my image
> > * update-alternatives is packed in update-alternatives-cworth (sub package of
> > opkg) which is not part of my image
> >
> > Isn't it required to have update-alternatives on the target
>
> Yes
>
> > because it is used
> > in postinst- / and postrm scripts?
>
> Those should be executed offline during build, so it's only for packages you install later on. Have a look at https://github.com/koenkooi/meta-angstrom/blob/master/recipes-images/angstrom/systemd-image.bb. That recipe will not include packagemanagement and u-a if ONLINE_PACKAGE_MANAGEMENT is set to none.
>
oe-core provides PACKAGE_GROUP_package-management/ for same. May be it
should be leveraged here ?
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
-Khem
prev parent reply other threads:[~2012-01-22 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 0:43 update-alternatives questions Andreas Müller
2012-01-17 9:07 ` Koen Kooi
2012-01-22 3:09 ` Khem Raj [this message]
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=20120122030934.GE27997@sakrah.homelinux.org \
--to=raj.khem@gmail.com \
--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 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.