From: Natanael Copa <natanael.copa@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Updating embedded systems
Date: Sat, 20 Jan 2007 15:24:07 +0100 [thread overview]
Message-ID: <1169303047.30407.13.camel@studio> (raw)
In-Reply-To: <45B2103E.5030209@wildgooses.com>
On Sat, 2007-01-20 at 12:51 +0000, Ed W wrote:
> I'm considering building a really stripped down environment to run
> Asterisk on an epia based machine. There are actually quite a lot of
> resources available on this box so it's not quite "embedded", but I was
> wondering what the recommended ways are of distributing updated packages
> if I went down either the GNAP route, or simply built a tiny system
> using ROOT=...?
>
> I notice the post previously which mentioned qmerge (which I hadn't
> previously heard of). Is this the best/only option? How do others
> update a base system once built?
I use portage only in the build system (chroot on my desktop) I make
binary packages that I convert to my own format
(http://apk-tools.sourceforge.net) That way I can append a
pre-install/post-install/pre-upgrade/post-upgrade script and easily
install/delete/upgrade packages in the runtime system.
http://alpinelinux.org
(It has packages for asterisk too btw...)
>
> Grateful for some pointers to research further
>
> Ed W
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-20 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 12:51 [gentoo-embedded] Updating embedded systems Ed W
2007-01-20 14:24 ` Natanael Copa [this message]
2007-01-22 1:09 ` [gentoo-embedded] odd behavior in '$SYSROOT' Christopher Friedt
2007-01-21 17:22 ` [gentoo-embedded] Updating embedded systems Jose Alberto
2007-01-25 17:36 ` Ed W
2007-01-25 17:48 ` Sune Kloppenborg Jeppesen
2007-01-26 10:06 ` Ed W
2007-01-26 11:59 ` Sune Kloppenborg Jeppesen
2007-01-30 8:27 ` josé Alberto Suárez López
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=1169303047.30407.13.camel@studio \
--to=natanael.copa@gmail.com \
--cc=gentoo-embedded@lists.gentoo.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