From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Changes to populate-volatile.sh / new volatiles class
Date: Thu, 23 Nov 2006 10:20:02 +1100 [thread overview]
Message-ID: <20061122232001.GA20265@twibble.org> (raw)
In-Reply-To: <4564D92B.6080500@dominion.kabel.utwente.nl>
On Thu, Nov 23, 2006 at 12:11:39AM +0100, Koen Kooi wrote:
> Jamie Lenehan schreef:
> > That update-alternatives thing on the
> > other hand I have definately been thinking about redoing in C when I
> > get a chance - it's painfully slow.
>
> The good folks from o-hand.conf gave us this:
> http://www.openembedded.org/filebrowser/org.openembedded.dev/packages/update-alternatives
>
> I think it would be wise to move to the dpkg version and if that's still to slow, re-do it
> in C.
The big issue I see with the dpkg version is that it's written in
perl... I think I'd prefer to have a slow version then be forced to
always install perl ;)
--
Jamie Lenehan <lenehan@twibble.org>
prev parent reply other threads:[~2006-11-22 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 4:32 Changes to populate-volatile.sh / new volatiles class Jamie Lenehan
2006-11-22 15:45 ` Paul Sokolovsky
2006-11-22 23:07 ` Jamie Lenehan
2006-11-22 23:11 ` Koen Kooi
2006-11-22 23:20 ` Jamie Lenehan [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=20061122232001.GA20265@twibble.org \
--to=lenehan@twibble.org \
--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