1 |
On Nov 1, 2005, at 4:01 PM, m h wrote: |
2 |
|
3 |
>>> |
4 |
>>> Well, if this is "round two" (which seems kind of weird since it's |
5 |
>>> backported from v2.1 to 2.0...). |
6 |
>> |
7 |
>> Well. the 2.1 branch has been officially killed, which is the version |
8 |
>> Haubi did his original work on, so Brian back ported it just so we |
9 |
>> could start testing out the ebuilds in an overlay and have a working |
10 |
>> prototype. |
11 |
> |
12 |
> Well, I'm interested in testing the 2.0 version if possible. |
13 |
|
14 |
Few more days, and should have an updated tarball to post for testing. |
15 |
|
16 |
> 3.0 |
17 |
> timeframe is start of next year? |
18 |
|
19 |
I think its mostly a question of manpower... |
20 |
|
21 |
> |
22 |
>> |
23 |
>>> I'm interested in tracking the |
24 |
>>> "official" version as closely as possible. Maybe I should test this |
25 |
>>> version out on FC4. What will "round three", etc, look like (are |
26 |
>>> there missing features, is it just testing, getting ebuilds |
27 |
>>> converted, |
28 |
>>> evangelism)? |
29 |
>>> |
30 |
>>> Kito- Could you please elaborate on the bootstrap process? |
31 |
>> |
32 |
>> Well, I started by building a toolchain manually in the prefix |
33 |
>> (gcc,cctools[apples linker/assembler], coreutils, make, python, bash |
34 |
>> and some others I'm forgetting), then configured and installed |
35 |
>> portage. Once portage was up and running I just started importing the |
36 |
>> base-system ebuilds to the overlay and merging as I went along. On a |
37 |
>> FC4 system, you could probably just use some symlinks instead of |
38 |
>> manually building a toolchain for bootstrap. |
39 |
>> |
40 |
> |
41 |
> Yeah on linux you could get by pretty easily. But if you want to |
42 |
> allow end users to add new archs (could be distro, or posix operating |
43 |
> system) wouldn't it be easier to have something like haubi's |
44 |
> bootstrapper? |
45 |
|
46 |
End users would simply download a stage tarball, just like a |
47 |
traditional gentoo install. People porting to other archs are welcome |
48 |
to try toolsbox, it was just more work for me to port toolsbox to |
49 |
Darwin than it was to build a toolchain manually and rebuild |
50 |
everything via portage. |
51 |
|
52 |
> |
53 |
>> I've finished the base-system ebuilds for a Darwin/OS X prefix, but |
54 |
>> for linux you will still need a few extra that I haven't done yet, |
55 |
>> like binutils, libtool, and gcc[1]. I'm going back and doing some |
56 |
>> cleanup and additional testing, should have it checked into svn later |
57 |
>> this week. Definitely want to get this working on as many archs as |
58 |
>> possible, so any help is welcome. |
59 |
>> |
60 |
>>> Perhaps |
61 |
>>> we could put it in the wiki? |
62 |
>> |
63 |
>> I was going to create a project page in xml under the gentoo-alt |
64 |
>> page, but a wiki might be a better idea, especially if a few other |
65 |
>> non-gentoo devs want to start helping out with the linux/aix/solaris |
66 |
>> stuff. |
67 |
>> |
68 |
> |
69 |
> Making the information public is better than no information. It seems |
70 |
> like it is better suited to be in the wiki right now, since end users |
71 |
> (non-gento devs) could add/edit/fix things in it. |
72 |
|
73 |
Sounds good to me. I'll probably add another page and leave the |
74 |
existing one that describes haubis method there for posterity. |
75 |
|
76 |
> |
77 |
>>> Regarding changes to ebuilds, yes I |
78 |
>>> agree small (or no) changes is preferred. |
79 |
>> |
80 |
>> Yeah, by far the biggest change needed right now is `make DESTDIR=$ |
81 |
>> {DEST} install`. I've made functions to address the ebuilds that |
82 |
>> don't use econf, so the changes are very very slight, and with some |
83 |
>> more work could probably even be lessened further. |
84 |
>> |
85 |
> |
86 |
> So DEST is PREFIX now? |
87 |
|
88 |
No. Most ebuilds do things in src_install() like `mv ${D}/usr/bin $ |
89 |
{D}/bin` and/or `[[ -e ${ROOT}/foo/bar]] && boof` |
90 |
|
91 |
So instead of being faced with a lot of changes in virtually every |
92 |
ebuild in the tree, we shifted the meaning of the vars slightly. |
93 |
So now, in the ebuild environment: |
94 |
|
95 |
D=${BUILDDIR}/image/${PREFIX} |
96 |
DEST=${BUILDDIR}/image |
97 |
ROOT=${ROOT}/${PREFIX} |
98 |
|
99 |
SO, really the only place you would ever use ${DEST} is `make DESTDIR= |
100 |
${DEST} install` as there should be no valid reason to ever touch the |
101 |
image dir directly. |
102 |
|
103 |
This drastically reduces the number of changes required to get most |
104 |
ebuilds prefix compliant. |
105 |
|
106 |
--Kito |
107 |
-- |
108 |
gentoo-osx@g.o mailing list |