1 |
There are two possibilities: |
2 |
|
3 |
- if the machines are identical, you can reuse the GRP in combination |
4 |
with the build plan representing the system which needs to be cloned |
5 |
- otherwise, (on another platform, different architecture) one can take |
6 |
the 'requirements' for the first system and ask portage(-ng) to come up |
7 |
with a new configuration/build plan which provides an explanation |
8 |
(proof) for the requirements. |
9 |
|
10 |
The first option is possible right now with portage if you pass the |
11 |
same USE and same packages to the emerge tool. |
12 |
|
13 |
Best regards, |
14 |
|
15 |
Pieter Van den Abeele |
16 |
|
17 |
|
18 |
On 10 Mar 2004, at 21:44, Anthony Dodson wrote: |
19 |
|
20 |
> Sorry if this is the wrong list for this question. |
21 |
> |
22 |
> If I build a system, optimized for the architecture without room for |
23 |
> backwards compatibility, containing all the software I want, what's an |
24 |
> easy |
25 |
> way to "clone" that build onto another machine with a different |
26 |
> architecture? |
27 |
> |
28 |
> For instance, how can one move the definition of the "world" class to |
29 |
> the |
30 |
> new machine (bootstrapped) and then emerge all that software at once? |
31 |
> Is |
32 |
> there a better approach? |
33 |
> |
34 |
> (Sounds like Tal Peer's GLEP 21 proposal might just solve this, but how |
35 |
> could it be done now?) |
36 |
> |
37 |
> Thanks, |
38 |
> Anthony Dodson |
39 |
> |
40 |
> IMPORTANT WARNING: |
41 |
> This e-mail is intended for the use of the person to whom it is |
42 |
> addressed |
43 |
> and may contain information that is privileged and confidential, the |
44 |
> disclosure of which is governed by applicable law. Dissemination, |
45 |
> distribution or copying of this information in an unauthorized manner |
46 |
> is |
47 |
> strictly prohibited. Sender accepts no liability for any damage caused |
48 |
> by |
49 |
> any virus transmitted by this e-mail. If you receive this in error, |
50 |
> please |
51 |
> notify the sender. |
52 |
> |
53 |
> |
54 |
> -- |
55 |
> gentoo-portage-dev@g.o mailing list |
56 |
> |
57 |
|
58 |
|
59 |
-- |
60 |
gentoo-portage-dev@g.o mailing list |