1 |
Kito wrote: |
2 |
> I would probably just use 'frameworks' as the name, the 'BP' prefix is |
3 |
> not generally used. |
4 |
|
5 |
Can do. |
6 |
|
7 |
<snip> |
8 |
> This wouldn't work as it isn't respecting ${D}. You want to have the |
9 |
> package install itself to ${D} and let portage handle touching the live fs. |
10 |
|
11 |
Ignored. :D |
12 |
|
13 |
<snip> |
14 |
> Hmmm, I wonder if we could make use of alternatives.eclass to handle the |
15 |
> symlinks for 'Current' |
16 |
|
17 |
I'm not familiar with this eclass; I'll check it out. |
18 |
|
19 |
<snip> |
20 |
> Probably shouldn't use `useq` or `ppc-macos` anymore. In fact, I'm not |
21 |
> even sure these need a conditional...but if they do, we should probably |
22 |
> `use userland_Darwin` instead. |
23 |
|
24 |
This syntax came from the example in |
25 |
http://dev.gentoo.org/~plasmaroo/devmanual/eclass-writing/. I agree it |
26 |
may not be the best approach. |
27 |
|
28 |
<snip> |
29 |
> The insert functions are useful, but I was also picturing a custom |
30 |
> src_install that automagically shuffled the files around in ${D} to |
31 |
> match the framework structure. For instance, check out some of your |
32 |
> existing frameworks of opensource projects like python, perl, and SDL. |
33 |
> You'll see they have somewhat of a standard unix-y layout |
34 |
> ('./usr{bin,lib,shared}') usually with symlinks like |
35 |
> `Documentation->Versions/Current/usr/share/doc |
36 |
> Headers->Versions/Current/usr/include`. |
37 |
|
38 |
I'll look at these. We may have conflicting ideas on how this eclass |
39 |
would be used. |
40 |
|
41 |
<snip> |
42 |
|
43 |
My vision for the used of this eclass is as follows: the library gets a |
44 |
USE flag, like "framework" or some such, which builds the library as a |
45 |
framework. These functions are used to help the ebuild author create |
46 |
the framework from the package files, as an ebuild author would use do* |
47 |
with a package lacking a standard `make install`. It's not clear if the |
48 |
activated USE flag would disable installation to a standard /usr/lib |
49 |
style location or simply add the construction of a framework. |
50 |
|
51 |
Let's further discussion! Exactly what does this eclass need to do? |
52 |
|
53 |
-Nick |
54 |
-- |
55 |
gentoo-osx@g.o mailing list |