1 |
Hi peter, thanks for your answer .... |
2 |
|
3 |
On Thu, 2008-09-04 at 00:35 +0200, Peter Stuge wrote: |
4 |
> Marcus Priesch wrote: |
5 |
> > i know catalyst is out there, but i doubt it is flexible enough ... |
6 |
> > but i would be fine off if you could teach me different ... |
7 |
> |
8 |
> I like catalyst and use stage4 for all targets. |
9 |
> |
10 |
> The nice thing about catalyst is 1. it's automated and 2. you can |
11 |
> pick and choose at which files you want to delete. |
12 |
|
13 |
yes, but thats exactly what portage and rsync also can handle ;) |
14 |
|
15 |
> > i also thought about building bin-pkgs and distributing them on the |
16 |
> > targets ... |
17 |
> |
18 |
> I'd like this too. In practice, catalyst uses tbz2s behind the |
19 |
> scenes, so everything doesn't have to be rebuilt every time. |
20 |
|
21 |
yes, but what about after a emerge --sync ?!?! - the problem with |
22 |
working with "outdated" portage trees is - despite that you dont have |
23 |
all the bugs fixed - that the .tgz's become unavailable after some |
24 |
time .... thats why i want to stay "tuned" ... |
25 |
|
26 |
furthermore updating a 2 year old gentoo system could be very time |
27 |
consuming .... thats also a reason why i want to stay up to date ... and |
28 |
i doubt that catalyst really supports this in a better way than plain |
29 |
portage does ... at least the reusability of the components is no plus |
30 |
than either ... |
31 |
|
32 |
|
33 |
> > is it possible to kepp all the .h and doc stuff out of a bin-pkg ?!?! |
34 |
> |
35 |
> Right, this is a good question, catalyst just makes tbz2s of the |
36 |
> normal packages and applies cleanup stuff at the end, so the tbz2s |
37 |
> themselves are not very deployable. |
38 |
|
39 |
yup ... what about "config-protect" - can this be "mis"used for such a |
40 |
function ?!?! |
41 |
|
42 |
regards, |
43 |
marcus. |