From: Sven Rebhan <odinshorse@googlemail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] tzdata & friends
Date: Mon, 14 Jun 2010 11:52:57 +0200 [thread overview]
Message-ID: <AANLkTikbJ87L4zVDeZVosNpzhXCh3q7N1P66NQlsZYxj@mail.gmail.com> (raw)
In-Reply-To: <1276286266.1875.39.camel@pr-laptop>
2010/6/11 Marcus Priesch <marcus@priesch.priv.at>:
> when i do it this way - syncing portage tree and updating selectively -
> i am not able to reproduce the entire build ... which - for me - is a no
> go ...
Well, if you want to keep versions stable for years you might want to
maintain an own portage tree and mount this via e.g. NFS on the
clients. To reproduce those builds you just need also to save the
versions of your build and do
for p in $(cat mypackagelist); do emerge =$p; done
However, you need to make sure that all source tarballs are avail
for years, which might be a problem as well. Furthermore, newer
versions of packages you _need_ to update (like your tzdata)
will probably require newer dependencies as well...
> thats why i wanted to use ubuntu lts - it's maintained with bug fixes
> for five years and doesnt change versions ... but as all of you might
> agree ... it's a no-go for other reasons ;)
I really think keeping versions stable for years and backporting fixes
is a lot of work and you need to make sure you have the resources
to maintain an own portage tree and backports of important fixes.
Sven
prev parent reply other threads:[~2010-06-14 10:10 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
2010-06-11 19:57 ` Marcus Priesch
2010-06-14 9:52 ` Sven Rebhan [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=AANLkTikbJ87L4zVDeZVosNpzhXCh3q7N1P66NQlsZYxj@mail.gmail.com \
--to=odinshorse@googlemail.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