On Mar 22, 2006, at 9:30 AM, Michael Haubenwallner wrote:
Hi,
related to renaming things:
Have there been any more thoughts or even implementations to [1]
about having a function to query the prefix of a required package ?
Thoughts for sure, no implementation yet though. My fear is this
would bring in many of the problems of interdomain stuff if we did it
'right'. i.e. repo-ids, etc. But perhaps I'm making it more complex
than need be, some extra data stored in the vdb and a simple lookup
tool could 'just work'. I think along with just being able to find
the filesystem location of a package, we might as well go all the way
and basically do an internal pkgconfig clone. This would allow stuff
like:
DEPEND="<my-dependency-2"
econf-or-src_compile() {
.../configure \
--prefix=$(eprefix) \
--with-my-dependency=$(eprefix "<my-dependency-2")
append-flags $(eprefix --cflags "<my-dependency-2")
append-ldflags $(eprifix --libs "<my-dependency-2")
}
Maybe...
My first goal are not the interdomain-deps, but to have a portage-
feature to install each non-system-package into a separate subdir
within
the same portage-domain.
Some of this would definitely overlap with some of the features Dirk
has asked for, i.e. merging a package to a selfcontained dir for
public distribution, self-contained OS X frameworks, etc.
Its a good idea, IMHO, but will be awhile before I personally will
start hacking on it. Others are welcome to give it a go =)
[1] http://thread.gmane.org/gmane.linux.gentoo.macosx/809
-- haubi
On Wed, 2006-03-22 at 12:47 +0100, Grobian wrote:
On a related note:
What about using ${EPREFIX} instead of ${PREFIX}? ${PREFIX} at least
clashes with the toolchain-funcs eclass, and might as well be used by
other packages.
Does it make sense to anyone?
On 20-03-2006 09:19:03 +0100, Grobian wrote:
On 19-03-2006 16:13:19 -0600, Kito wrote:
Howdy,
I forgot to mention this at the meeting. I found a few packages
(not in
portage currently thankfully) that have namespace collisions
with the ${DEST}
var. My thought is to change it to ${DD}, as in 'DESTDIR'.
Thoughts? Better idea for a name?
The only thing that comes to my mind as alternative is "${EDEST}".
Might be slightly more self-explanatory. I don't care much about
which
of the two it will become, as long as the change is done atomic ;)
--
Fabian Groffen
Gentoo for Mac OS X Project
--
[email protected] mailing list
--Kito
--
[email protected] mailing list
