From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OEDEM 2009 summary: Package management
Date: Wed, 11 Nov 2009 21:33:32 +0100 [thread overview]
Message-ID: <20091111203332.GC11484@jama> (raw)
In-Reply-To: <1257959521.25369.393.camel@lenovo.internal.reciva.com>
On Wed, Nov 11, 2009 at 05:12:01PM +0000, Phil Blundell wrote:
> This was the last session of the OEDEM schedule and the number of
> participants was much reduced compared to the previous ones. Partly as
> a result of that it was also very short.
>
> Key issue: opkg is the defacto standard for package management in
> OE-derived distros but its quality is perceived as low. What can we do
> about this?
Today I've "fixed" one problem we had with opkg in shr.
opkg installs own version of update-alternatives
its the same script as the one packaged as update-alternatives-cworth
its installed to /usr/bin (update-alternatives-cworth is using
/usr/sbin so in PATH is after version from opkg)
I've patch for update-alternatives-cworth to use alternative which was
installed last if there is no alternative with higher priority (see
http://cgit.openembedded.net/cgit.cgi/openembedded/commit/?h=shr/merge&id=6c1ed757c1498aff5b4b1b876332d2981f0855a1
)
And it was really confusing to have 2 simillar update-alternatives
scripts in image.
So it should be removed from opkg as I did in
http://cgit.openembedded.net/cgit.cgi/openembedded/commit/?h=shr/merge&id=376cca189eed7a13de5a348e630c0af274c4704b
http://cgit.openembedded.net/cgit.cgi/openembedded/commit/?h=shr/merge&id=416f6e5f5cfa23f0b3ae731af5c2a1dcd1e27189
or opkg should provide virtual/update-alternatives as distros are using
preferred_provider for that already.
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next prev parent reply other threads:[~2009-11-11 20:35 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 [this message]
2009-11-13 13:15 ` Martin Jansa
2009-11-16 10:57 ` Florian Boor
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=20091111203332.GC11484@jama \
--to=martin.jansa@gmail.com \
--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.