1 |
I have to agree with everyone else. Especially if you're trying to |
2 |
provide a foundation for a number of people, building on top of a |
3 |
variety of moving targets, i.e. peoples' OSs, will be a nightmare. |
4 |
|
5 |
drobbins says he's going to rewrite Metro in the next few months. Once |
6 |
he does, I might be interested in working on some scripts for setting |
7 |
up prefix instances. |
8 |
|
9 |
Peter |
10 |
|
11 |
On Mon, Mar 29, 2010 at 9:03 AM, Jeremy Olexa <darkside@g.o> wrote: |
12 |
> |
13 |
> On Mon, 29 Mar 2010 17:50:20 +0200, Michael Haubenwallner |
14 |
> <haubi@g.o> wrote: |
15 |
>> Third hint: |
16 |
>> Having that many different systems and users feels like becoming a |
17 |
>> maintenance nightmare when trying to use as much as possible |
18 |
>> packages from the host system. |
19 |
> |
20 |
> Hello, |
21 |
> I would even go one step farther and say it is VERY difficult to provide |
22 |
> such a setup with host tools. For example, can one guarantee that every |
23 |
> host that someone uses has bash-3.2 or greater? Half of my systems don't. |
24 |
> So, I would argue that you should have more tools in the target prefix |
25 |
> rather than less from a supportability standpoint (where support is coming |
26 |
> from you ;) ). It goes without saying that the Gentoo Prefix team is never |
27 |
> able to support this due to all the variables. |
28 |
> |
29 |
> With that being said, please first build up a Gentoo Prefix environment |
30 |
> like it was intended and then try to replicate it with host tools. You will |
31 |
> need the experience of knowing how it is suppose to work first and |
32 |
> foremost. |
33 |
> |
34 |
> Good luck, |
35 |
> Jeremy |
36 |
> |
37 |
> |