public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marcus Priesch <marcus@priesch.priv.at>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] tzdata & friends
Date: Fri, 11 Jun 2010 17:15:06 +0200	[thread overview]
Message-ID: <1276269306.1875.35.camel@pr-laptop> (raw)
In-Reply-To: <AANLkTilMnFqfWO7TqXEQsp_wxKR9uEAaMX_UTacAqygn@mail.gmail.com>

Hi Sven,

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
tree ?!?

> 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
> http://gentoo.mindzoo.de
> http://git.overlays.gentoo.org/gitweb/?p=proj/embedded-cross.git;a=summary

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 ;)))

regards,
marcus.






  reply	other threads:[~2010-06-11 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 10:59 [gentoo-embedded] tzdata & friends Marcus Priesch
2010-06-11  8:30 ` Sven Rebhan
2010-06-11 15:15   ` Marcus Priesch [this message]
2010-06-11 19:57   ` Marcus Priesch
2010-06-14  9:52     ` Sven Rebhan

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=1276269306.1875.35.camel@pr-laptop \
    --to=marcus@priesch.priv.at \
    --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