1 |
On Nov 1, 2005, at 1:16 PM, m h wrote: |
2 |
|
3 |
> On 10/31/05, Kito <kito@g.o> wrote: |
4 |
>> |
5 |
>> On Oct 31, 2005, at 6:32 PM, Brian Harring wrote: |
6 |
>> |
7 |
>>> On Mon, Oct 31, 2005 at 04:16:44PM -0800, m h wrote: |
8 |
>>> |
9 |
>>> Should be usable in both cases. Literally, the prefix stable |
10 |
>>> patch is |
11 |
>>> chunks of my 2.1 work and haubi's work torn out and integrated into |
12 |
>>> 2.0 |
13 |
>>> for prototype demonstration. |
14 |
>> |
15 |
>> Those last 2 words should be stressed... don't want anyone getting |
16 |
>> false ideas of whats being done here... |
17 |
> |
18 |
> Well, if this is "round two" (which seems kind of weird since it's |
19 |
> backported from v2.1 to 2.0...). |
20 |
|
21 |
Well. the 2.1 branch has been officially killed, which is the version |
22 |
Haubi did his original work on, so Brian back ported it just so we |
23 |
could start testing out the ebuilds in an overlay and have a working |
24 |
prototype. |
25 |
|
26 |
> I'm interested in tracking the |
27 |
> "official" version as closely as possible. Maybe I should test this |
28 |
> version out on FC4. What will "round three", etc, look like (are |
29 |
> there missing features, is it just testing, getting ebuilds converted, |
30 |
> evangelism)? |
31 |
> |
32 |
> Kito- Could you please elaborate on the bootstrap process? |
33 |
|
34 |
Well, I started by building a toolchain manually in the prefix |
35 |
(gcc,cctools[apples linker/assembler], coreutils, make, python, bash |
36 |
and some others I'm forgetting), then configured and installed |
37 |
portage. Once portage was up and running I just started importing the |
38 |
base-system ebuilds to the overlay and merging as I went along. On a |
39 |
FC4 system, you could probably just use some symlinks instead of |
40 |
manually building a toolchain for bootstrap. |
41 |
|
42 |
I've finished the base-system ebuilds for a Darwin/OS X prefix, but |
43 |
for linux you will still need a few extra that I haven't done yet, |
44 |
like binutils, libtool, and gcc[1]. I'm going back and doing some |
45 |
cleanup and additional testing, should have it checked into svn later |
46 |
this week. Definitely want to get this working on as many archs as |
47 |
possible, so any help is welcome. |
48 |
|
49 |
> Perhaps |
50 |
> we could put it in the wiki? |
51 |
|
52 |
I was going to create a project page in xml under the gentoo-alt |
53 |
page, but a wiki might be a better idea, especially if a few other |
54 |
non-gentoo devs want to start helping out with the linux/aix/solaris |
55 |
stuff. |
56 |
|
57 |
> Regarding changes to ebuilds, yes I |
58 |
> agree small (or no) changes is preferred. |
59 |
|
60 |
Yeah, by far the biggest change needed right now is `make DESTDIR=$ |
61 |
{DEST} install`. I've made functions to address the ebuilds that |
62 |
don't use econf, so the changes are very very slight, and with some |
63 |
more work could probably even be lessened further. |
64 |
|
65 |
> I went ahead and installed |
66 |
> apache2 in my prefixed environment and it was relatively |
67 |
> straightforward. |
68 |
|
69 |
Yeah, I'm having great luck so far, running gtk+, jack, and ardour |
70 |
out of the prefix with no problems and very minor ebuild changes. |
71 |
|
72 |
> |
73 |
> Brian- Do you have any idea of the roadmap for prefix getting into |
74 |
> portage? Would it possibly get into 2.0? 2.1? Rewrite? What will |
75 |
> determine this? |
76 |
|
77 |
I'll let Brian answer this, but I'm fairly certain there is no chance |
78 |
of this making it into the 2.0 series, 2.1 is dead, so 3.0 will have |
79 |
to be our saviour (boooo! hsssss! bad pun) |
80 |
|
81 |
--Kito |
82 |
|
83 |
|
84 |
[1] I chose to use the apple branch of gcc, as most upstream packages |
85 |
have started expecting it on Darwin systems, and have started using |
86 |
apple-specific flags such as -mdynamic-no-pic and -no-cpp-precomp and |
87 |
-faltivec, so I figured this is the path of least resistance. Plus |
88 |
this allows us to take advantage of Frameworks... |
89 |
|
90 |
-- |
91 |
gentoo-osx@g.o mailing list |