From: Florian Boor <florian.boor@kernelconcepts.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OEDEM 2009 summary: Package management
Date: Mon, 16 Nov 2009 11:57:08 +0100 [thread overview]
Message-ID: <4B013004.8010602@kernelconcepts.de> (raw)
In-Reply-To: <1257959521.25369.393.camel@lenovo.internal.reciva.com>
Hi,
Phil Blundell schrieb:
> PB: opkg generally performs OK within its own "comfort envelope". Main
> triggers for badness seem to be online upgrades, and the requirement to
> make a decision between two alternatives. If you stay away from those
> things and use opkg only for image construction then it is not so bad.
I have not tried much online upgrades for some time but I ran into package
selection issues lately. We always suffered from the problem that opkg failed
with an error message if the same package was available with two different
architectures... but this is fixed upstream now.
greetings
Florian
--
The dream of yesterday Florian Boor
is the hope of today Tel: +49 271-771091-15
and the reality of tomorrow. Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904] florian.boor@kernelconcepts.de
http://www.kernelconcepts.de/en
prev parent reply other threads:[~2009-11-16 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 17:12 OEDEM 2009 summary: Package management Phil Blundell
2009-11-11 20:33 ` Martin Jansa
2009-11-13 13:15 ` Martin Jansa
2009-11-16 10:57 ` Florian Boor [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=4B013004.8010602@kernelconcepts.de \
--to=florian.boor@kernelconcepts.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 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.