1 |
On Mar 22, 2006, at 9:30 AM, Michael Haubenwallner wrote: |
2 |
|
3 |
> Hi, |
4 |
> |
5 |
> related to renaming things: |
6 |
> |
7 |
> Have there been any more thoughts or even implementations to [1] |
8 |
> about having a function to query the prefix of a required package ? |
9 |
|
10 |
Thoughts for sure, no implementation yet though. My fear is this |
11 |
would bring in many of the problems of interdomain stuff if we did it |
12 |
'right'. i.e. repo-ids, etc. But perhaps I'm making it more complex |
13 |
than need be, some extra data stored in the vdb and a simple lookup |
14 |
tool could 'just work'. I think along with just being able to find |
15 |
the filesystem location of a package, we might as well go all the way |
16 |
and basically do an internal pkgconfig clone. This would allow stuff |
17 |
like: |
18 |
|
19 |
DEPEND="<my-dependency-2" |
20 |
|
21 |
econf-or-src_compile() { |
22 |
.../configure \ |
23 |
--prefix=$(eprefix) \ |
24 |
--with-my-dependency=$(eprefix "<my-dependency-2") |
25 |
|
26 |
append-flags $(eprefix --cflags "<my-dependency-2") |
27 |
append-ldflags $(eprifix --libs "<my-dependency-2") |
28 |
} |
29 |
|
30 |
Maybe... |
31 |
|
32 |
> |
33 |
> My first goal are not the interdomain-deps, but to have a portage- |
34 |
> feature to install each non-system-package into a separate subdir |
35 |
> within |
36 |
> the same portage-domain. |
37 |
|
38 |
Some of this would definitely overlap with some of the features Dirk |
39 |
has asked for, i.e. merging a package to a selfcontained dir for |
40 |
public distribution, self-contained OS X frameworks, etc. |
41 |
|
42 |
Its a good idea, IMHO, but will be awhile before I personally will |
43 |
start hacking on it. Others are welcome to give it a go =) |
44 |
|
45 |
> |
46 |
> [1] http://thread.gmane.org/gmane.linux.gentoo.macosx/809 |
47 |
> |
48 |
> -- haubi |
49 |
> |
50 |
> On Wed, 2006-03-22 at 12:47 +0100, Grobian wrote: |
51 |
>> On a related note: |
52 |
>> What about using ${EPREFIX} instead of ${PREFIX}? ${PREFIX} at least |
53 |
>> clashes with the toolchain-funcs eclass, and might as well be used by |
54 |
>> other packages. |
55 |
>> |
56 |
>> Does it make sense to anyone? |
57 |
>> |
58 |
>> |
59 |
>> On 20-03-2006 09:19:03 +0100, Grobian wrote: |
60 |
>>> On 19-03-2006 16:13:19 -0600, Kito wrote: |
61 |
>>>> Howdy, |
62 |
>>>> |
63 |
>>>> I forgot to mention this at the meeting. I found a few packages |
64 |
>>>> (not in |
65 |
>>>> portage currently thankfully) that have namespace collisions |
66 |
>>>> with the ${DEST} |
67 |
>>>> var. My thought is to change it to ${DD}, as in 'DESTDIR'. |
68 |
>>>> |
69 |
>>>> Thoughts? Better idea for a name? |
70 |
>>> |
71 |
>>> The only thing that comes to my mind as alternative is "${EDEST}". |
72 |
>>> Might be slightly more self-explanatory. I don't care much about |
73 |
>>> which |
74 |
>>> of the two it will become, as long as the change is done atomic ;) |
75 |
>>> |
76 |
>>> |
77 |
>> |
78 |
>> -- |
79 |
>> Fabian Groffen |
80 |
>> Gentoo for Mac OS X Project |
81 |
> |
82 |
> -- |
83 |
> gentoo-osx@g.o mailing list |
84 |
> |
85 |
|
86 |
--Kito |
87 |
|
88 |
|
89 |
|
90 |
|
91 |
-- |
92 |
gentoo-osx@g.o mailing list |