public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marcus Priesch <marcus@priesch.priv.at>
To: gentoo embedded <gentoo-embedded@lists.gentoo.org>
Subject: [gentoo-embedded] tzdata & friends
Date: Thu, 10 Jun 2010 12:59:12 +0200	[thread overview]
Message-ID: <1276167552.2012.591.camel@pr-laptop> (raw)

Hi Guys,

One annoying thing i encountered in the past when using gentoo on a
linux box was staying up to date with packages (like timzonedata &
pytz).

when you want to stay in sync with the portage tree - you also have to
update a lot of other packages from time to time ... which alters the
system and possibly needs other work to be involved to keep it
running ... in the end you have to test the whole behaviour again and
the customer gets a "new" system - which is lot of work and hard to
argument ;)

when you dont update, timezonedata could be out of date ... and the
customer discovers that DST change did not happen correctly ... which is
also hard to argument ;)

so basically i am searching for a solution where i can update "only"
relevant packages from time to time (like timezonedata) but leave the
rest of the system untouched ... customers boxes are running in a
private lan so security is not really a concern ;)

currently the only way i can think of is to maintain a private portage
tree and update packages selectively - as long as the dependencies dont
require more ... are there any other possibilities ?!? how are you
handling such situations ?!?

the other question is on distributing the packages to the boxes:

in the past i had a full gentoo system where i updated and compiled and
rsynced selectively to the boxes - but with full dev environment which
was clearly a waste of storage space, time and bandwith.

currently i have one --root created and stripped down environment which
i rsync to the boxes (without gcc, portage tree, kernel sources) ...
plus i need a gentoo system for building where i merge change into the
portage tree from time to time ...

the complexity of this is why i took a look at debian/ubuntu for this
kind of task ... but ... for me it's not an option as it's tooo
inflexible.

after all i should come up with a solution where the customer can do the
update on its own ... 

so any ideas and/or discussion would be very welcome !!!

regards,
marcus.






             reply	other threads:[~2010-06-10 11:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 10:59 Marcus Priesch [this message]
2010-06-11  8:30 ` [gentoo-embedded] tzdata & friends Sven Rebhan
2010-06-11 15:15   ` Marcus Priesch
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=1276167552.2012.591.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