1 |
Hey Richard, |
2 |
|
3 |
Richard Geary <richardg.work@×××××.com> writes: |
4 |
|
5 |
> Thanks for replying to me about bootstrap script. Separately, I have a |
6 |
> existential question about Prefix - I thought I'd email you offline so |
7 |
> you can reply with impunity, but I can send it to the gentoo-alt list |
8 |
> if you'd prefer. |
9 |
|
10 |
Ok, let's make it to the list. |
11 |
|
12 |
> Over the past 2 years I've rolled my own Prefix-style system for my |
13 |
> company for building, packaging (binaries), disting and installing on |
14 |
> our linux OSs. |
15 |
|
16 |
Amazing, that's definitely a lot of work. |
17 |
|
18 |
> I'm reaching a point where my team are going to rewrite it for version |
19 |
> 2, but it's still in the design & prototype stages. My question is, if |
20 |
> you were to redesign Gentoo Prefix from scratch, what would you |
21 |
> change? |
22 |
|
23 |
Well, I am not the best person to answer this question. @grobian might |
24 |
have a deeper view on the overall design. |
25 |
|
26 |
IMHO, the Prefix is as good as Gentoo itself. Even if I were to |
27 |
reinvent it, it would still be like this. That said, there are many |
28 |
things left to be done apart from timely update routines to make it more |
29 |
useful, for example: |
30 |
|
31 |
1. a full synchronization with the gentoo-x86 tree, i.e. retiring of |
32 |
Prefix overlay. (@ottxor) |
33 |
2. a semi-automatic bootstrap procedure for RAP. (@redlizard) |
34 |
3. a stabilization policy making it manageable as well as of production |
35 |
quality by default (ultimate goal) |
36 |
|
37 |
So, I think we are on the right path. |
38 |
|
39 |
> Our current system builds & installs each package to its own |
40 |
> package/version directory, using RPATHs to link dependencies. We're |
41 |
> moving towards a traditional lib/bin/include directory structure with |
42 |
> manual selection of version alternatives. I found that dlopen .so |
43 |
> loading & ABI versioning becomes impossible with separate |
44 |
> package/version directories. |
45 |
|
46 |
Yeah, I like the traditional lib/bin/include directory style. And it |
47 |
would be rewarding for the Prefix team to see that it could save part of |
48 |
your effort. |
49 |
|
50 |
Cheers, |
51 |
Benda |