1 |
Hi, |
2 |
|
3 |
related to renaming things: |
4 |
|
5 |
Have there been any more thoughts or even implementations to [1] |
6 |
about having a function to query the prefix of a required package ? |
7 |
|
8 |
My first goal are not the interdomain-deps, but to have a portage- |
9 |
feature to install each non-system-package into a separate subdir within |
10 |
the same portage-domain. |
11 |
|
12 |
[1] http://thread.gmane.org/gmane.linux.gentoo.macosx/809 |
13 |
|
14 |
-- haubi |
15 |
|
16 |
On Wed, 2006-03-22 at 12:47 +0100, Grobian wrote: |
17 |
> On a related note: |
18 |
> What about using ${EPREFIX} instead of ${PREFIX}? ${PREFIX} at least |
19 |
> clashes with the toolchain-funcs eclass, and might as well be used by |
20 |
> other packages. |
21 |
> |
22 |
> Does it make sense to anyone? |
23 |
> |
24 |
> |
25 |
> On 20-03-2006 09:19:03 +0100, Grobian wrote: |
26 |
> > On 19-03-2006 16:13:19 -0600, Kito wrote: |
27 |
> > > Howdy, |
28 |
> > > |
29 |
> > > I forgot to mention this at the meeting. I found a few packages (not in |
30 |
> > > portage currently thankfully) that have namespace collisions with the ${DEST} |
31 |
> > > var. My thought is to change it to ${DD}, as in 'DESTDIR'. |
32 |
> > > |
33 |
> > > Thoughts? Better idea for a name? |
34 |
> > |
35 |
> > The only thing that comes to my mind as alternative is "${EDEST}". |
36 |
> > Might be slightly more self-explanatory. I don't care much about which |
37 |
> > of the two it will become, as long as the change is done atomic ;) |
38 |
> > |
39 |
> > |
40 |
> |
41 |
> -- |
42 |
> Fabian Groffen |
43 |
> Gentoo for Mac OS X Project |
44 |
|
45 |
-- |
46 |
gentoo-osx@g.o mailing list |