1 |
The PORTAGE_BINHOST option is quit time consuming on emerges. But, if |
2 |
you're only doing it once in awhile, in batched sets, it should be |
3 |
just fine. The reason it takes so long is that it has to do an FTP |
4 |
listing of the remote host, cache that info, and then finally it'll do |
5 |
the merging. |
6 |
|
7 |
I was doing that quite a bit in times past. But, you have to make |
8 |
sure you are using the same use flags on EVERY host. Also, I did have |
9 |
issues where emerge would refuse to use a binary package, and instead |
10 |
would re-build it. I think it was due to using the --newuse |
11 |
functionality, and/or the -u (update) functionality. |
12 |
|
13 |
|
14 |
On 10/13/06, Timothy A. Holmes <tholmes@×××××××××.net> wrote: |
15 |
> >> On Friday 13 October 2006 15:16, Timothy A. Holmes wrote: |
16 |
> > > I was reading the thread on the lightweight gentoo system. |
17 |
> > This to a |
18 |
> > > degree meshed with what a friend and I have been talking about. |
19 |
> > > Essentially setting up a standard image for all of my |
20 |
> > gentoo servers, |
21 |
> > > and stage 4ing (is that a word?) that image to the servers. |
22 |
> > Once they |
23 |
> > > are in production, building updates etc in a dedicated build |
24 |
> > > environment and simply rolling out binaries to the boxes as |
25 |
> > they are needed. |
26 |
> > > |
27 |
> > > The concept sounds really good, giving me the ability to do |
28 |
> > > (relatively) fast updates with binaries on the production servers, |
29 |
> > > after they have been through testing, with out tying up |
30 |
> > resouces, and |
31 |
> > > (more importantly) being able to fully test them prior to |
32 |
> > putting them into production. |
33 |
> > > |
34 |
> > > If anyone has done this type of thing, or has references, links, |
35 |
> > > pointers etc I would REALLY appreciate them. |
36 |
> > |
37 |
> > I haven't done any stage4 stuff so no clue about how to do |
38 |
> > that. I only know that it's possible. But for the rest of it |
39 |
> > [1] should give you a hint... |
40 |
> > |
41 |
> > [1] |
42 |
> > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2& |
43 |
> chap=3#doc_chap4 |
44 |
> > |
45 |
> > -- |
46 |
> > Bo Andresen |
47 |
> > |
48 |
> |
49 |
> Bo: |
50 |
> |
51 |
> The stage 4 stuff is quite easy and I do that routinely. If you want |
52 |
> links or suggestions on how to do it I'll be glad to try to help -- its |
53 |
> sped up my life considerably. It was the separate build host etc stuff |
54 |
> that I was looking for. That section out of the handbook looks good |
55 |
> --I'll start playing with it in a dev environment hopefully this weekend |
56 |
> -- thanks for the pointer |
57 |
> |
58 |
> TIM |
59 |
> |
60 |
> |
61 |
> Timothy A. Holmes |
62 |
> IT Manager / Network Admin / Web Master / Computer Teacher |
63 |
> |
64 |
> Medina Christian Academy |
65 |
> A Higher Standard... |
66 |
> |
67 |
> |
68 |
> -- |
69 |
> gentoo-user@g.o mailing list |
70 |
> |
71 |
> |
72 |
-- |
73 |
gentoo-user@g.o mailing list |