Am Freitag, den 11.06.2010, 10:30 +0200 schrieb Sven Rebhan:
> Hmmm, why don't you just update packages selectively like
> emerge -u tzdata <other packages you want updated>
yes, but arent chances great that over time ther needs to be a major
e.g. python upgrade as the old version just disappeared from the portage
> instead of updating everything? Note: leave out the --deep option.
> I did this for years on my desktop machine and only updated world
> from time to time. Furthermore, you can mask package versions in
> $ROOT/etc/portage/package.mask if you really have something
> you want to ignore.
yes, i know - but same thing as above ... when kernel trees disappear in
the portage tree ... you need to upgrade anyway ... thats why i thought
of having a seperate portage tree managed ...
> Ummm, the way I (and others) do it is building binpkgs in the
> cross-compile environment and then update the embedded
> system(s) using these binpkgs. This way your customer can
> update from your FTP/HTTP/... binpkg server with
> emerge -ug <packages>. The only thing you have to make
> sure is, you either mask all package you don't want them to
> update or to provide all updateable packages as binaries.
yes but you need a portage tree - and a sync'ed portage tree on the
clients to install binpkgs, or ?!?
> You might want to have a look at
thanks a lot - i will give it a try
> even though the documentation is a bit outdated. *hint*
> P.S.: Maybe you also want to join #gentoo-embedded on freenode!?!
yes, not now - as i must leave ... but maybe next week ...
however, things turned out that i need to have the complete "system"
target on my --root installed rootfs (as i need some c python package
which wants to compile itself ...
and, yes, i love the idea of having a script running for a couple of
hours to create a virgin rootfs out of nothing