1 |
On Dec 14, 2005, at 7:48 PM, m h wrote: |
2 |
|
3 |
> Another question. PORTDIR is not getting the prefixed value in |
4 |
> portage.py. Kito, how |
5 |
> are you setting this? Are you using an env variable? |
6 |
|
7 |
What do you mean 'in portage.py' ? The constants are defined in pym/ |
8 |
portage_const.py and pym/portage_const_autotool.py (the latter being |
9 |
defined by the options originally passed to configure) |
10 |
|
11 |
I'm setting PREFIX at the top of ${PREFIX}/etc/make.conf and setting |
12 |
everything else accordingly (my PORTDIR is a cvs checkout of the |
13 |
mainline portage tree, PORTDIR_OVERLAY is the snapshot I posted) |
14 |
|
15 |
Right now, the defaults are all still the same as vanilla portage, |
16 |
i.e. /usr/* |
17 |
|
18 |
Obviously hardcoding in make.conf breaks the ability to merge to |
19 |
arbitrary locations from the command line like `PREFIX=/tmp emerge -v |
20 |
boof` |
21 |
|
22 |
> |
23 |
> |
24 |
> On 12/14/05, m h <sesquile@×××××.com> wrote: |
25 |
>> So I have a question: |
26 |
>> Where can I get the ${PREFIX}/usr/local/portage/profiles directory |
27 |
>> from to bootstrap? Haubi and Kito both have them, but where did they |
28 |
>> get them from? It's not bundled with portage itself nor is it in the |
29 |
>> stage1.... |
30 |
|
31 |
The macos profile is in PORTDIR/profiles/default-darwin/macos/prefix. |
32 |
You can either put the stuff from toolsbox in your profiles |
33 |
package.provided, or make sure FEATURES="-collision-protect" and use |
34 |
the ebuilds from the prefix tree to recompile your toolchain with |
35 |
portage. |
36 |
|
37 |
--Kito |
38 |
|
39 |
-- |
40 |
gentoo-osx@g.o mailing list |