Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Sebastian Spaeth <Sebastian@SSpaeth.de>
To: openembedded-devel@lists.openembedded.org
Subject: BAD_RECOMMENDATIONS is broken
Date: Wed, 18 Nov 2009 11:26:56 +0100	[thread overview]
Message-ID: <4B03CBF0.5010000@SSpaeth.de> (raw)

minimal.conf has
DISTRO_EXTRA_RRECOMMENDS += "[...] avahi-daemon avahi-autoipd [...]"
which leads to task-distro-base recommending those packages.

Trying to override this with
BAD_RECOMMENDATIONS="avahi-daemon avahi-autoipd"
does not wotk though, it's still pulled in.

This is what rootfs_ipk.bbclass does:

        STATUS=${IMAGE_ROOTFS}${libdir}/opkg/status
        # prime the status file with bits that we don't want
        for i in ${BAD_RECOMMENDATIONS}; do
                echo "Package: $i" >> $STATUS
                echo "Architecture: ${TARGET_ARCH}" >> $STATUS
                echo "Status: deinstall ok not-installed" >> $STATUS
                echo >> $STATUS
        done

which actually writes out the correct stuff

+STATUS=/home/[...]/tmp/rootfs/shr-image/usr/lib/opkg/status
+for i in avahi-daemon avahi-autoipd
+echo 'Package: avahi-daemon'
+echo 'Architecture: arm'
+echo 'Status: deinstall ok not-installed'
+echo
+for i in avahi-daemon avahi-autoipd
+echo 'Package: avahi-autoipd'
+echo 'Architecture: arm'
+echo 'Status: deinstall ok not-installed'
+echo

However, when task-distro-base is installed it still pulls in
avahi-daemon, so I think this way of handling BAD_RECOMMENDATIONS is
broken by different opkg behavior.

Any solution (besides removing avahi from minimal.conf where I don't
think it should be in the first place)?

spaetz



             reply	other threads:[~2009-11-18 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 10:26 Sebastian Spaeth [this message]
2009-11-18 10:35 ` BAD_RECOMMENDATIONS is broken (opkg issue) Sebastian Spaeth
2009-11-18 21:20   ` Graham Gower
2009-11-18 22:12     ` Phil Blundell
2009-11-18 22:55       ` Graham Gower
2010-02-24 20:58         ` Denys Dmytriyenko

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=4B03CBF0.5010000@SSpaeth.de \
    --to=sebastian@sspaeth.de \
    --cc=openembedded-devel@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