1 |
Hi Guys, |
2 |
|
3 |
One annoying thing i encountered in the past when using gentoo on a |
4 |
linux box was staying up to date with packages (like timzonedata & |
5 |
pytz). |
6 |
|
7 |
when you want to stay in sync with the portage tree - you also have to |
8 |
update a lot of other packages from time to time ... which alters the |
9 |
system and possibly needs other work to be involved to keep it |
10 |
running ... in the end you have to test the whole behaviour again and |
11 |
the customer gets a "new" system - which is lot of work and hard to |
12 |
argument ;) |
13 |
|
14 |
when you dont update, timezonedata could be out of date ... and the |
15 |
customer discovers that DST change did not happen correctly ... which is |
16 |
also hard to argument ;) |
17 |
|
18 |
so basically i am searching for a solution where i can update "only" |
19 |
relevant packages from time to time (like timezonedata) but leave the |
20 |
rest of the system untouched ... customers boxes are running in a |
21 |
private lan so security is not really a concern ;) |
22 |
|
23 |
currently the only way i can think of is to maintain a private portage |
24 |
tree and update packages selectively - as long as the dependencies dont |
25 |
require more ... are there any other possibilities ?!? how are you |
26 |
handling such situations ?!? |
27 |
|
28 |
the other question is on distributing the packages to the boxes: |
29 |
|
30 |
in the past i had a full gentoo system where i updated and compiled and |
31 |
rsynced selectively to the boxes - but with full dev environment which |
32 |
was clearly a waste of storage space, time and bandwith. |
33 |
|
34 |
currently i have one --root created and stripped down environment which |
35 |
i rsync to the boxes (without gcc, portage tree, kernel sources) ... |
36 |
plus i need a gentoo system for building where i merge change into the |
37 |
portage tree from time to time ... |
38 |
|
39 |
the complexity of this is why i took a look at debian/ubuntu for this |
40 |
kind of task ... but ... for me it's not an option as it's tooo |
41 |
inflexible. |
42 |
|
43 |
after all i should come up with a solution where the customer can do the |
44 |
update on its own ... |
45 |
|
46 |
so any ideas and/or discussion would be very welcome !!! |
47 |
|
48 |
regards, |
49 |
marcus. |