| 1 |
On 04-10-2013 08:58:06 +0200, Michael Haubenwallner wrote: |
| 2 |
> > Can't we just blacklist it in startprefix? How does it end up in the |
| 3 |
> > env anyway? Is it during bootstrap? then just blacklist it in |
| 4 |
> > bootstrap-prefix.sh |
| 5 |
> |
| 6 |
> Anyone starting with the host's loginshell environment does have it set. |
| 7 |
> |
| 8 |
> For automation purposes it is necessary to be able to run the Prefix environment |
| 9 |
> simply by "source EPREFIX/etc/profile", so actually one shell's env cumulates: |
| 10 |
> source /etc/profile |
| 11 |
> source @GENTOO_PORTAGE_EPREFIX@/etc/profile # portage builtin |
| 12 |
> source $EPREFIX/etc/profile # envvar with prefix-chaining (like cross-prefix) |
| 13 |
> |
| 14 |
> Building some non ebuild-ified but autotoolized application using this env setup |
| 15 |
> will see CONFIG_PATH and fail. |
| 16 |
> |
| 17 |
> > I'm probably missing something here. It feels like the PKG_CONFIG_PATH |
| 18 |
> > thing a bit. |
| 19 |
> |
| 20 |
> Indeed, they're on the same level. And here I find PKG_CONFIG_PATH being set in both |
| 21 |
> @GENTOO_PORTAGE_EPREFIX@'s and $EPREFIX's etc/env.d/00basic, unsure if we (still) do |
| 22 |
> that in vanilla Prefix. |
| 23 |
|
| 24 |
% grep PKG_CONFIG_PATH $EPREFIX/etc/env.d/* |
| 25 |
/Volumes/Scratch/Gentoo/etc/env.d/99pkgconfig:PKG_CONFIG_PATH=/Volumes/Scratch/Gentoo/usr/lib/pkgconfig:/Volumes/Scratch/Gentoo/usr/share/pkgconfig |
| 26 |
% qfile /Volumes/Scratch/Gentoo/etc/env.d/99pkgconfig |
| 27 |
dev-util/pkgconfig (/Volumes/Scratch/Gentoo/etc/env.d/99pkgconfig) |
| 28 |
|
| 29 |
That said, we could either have autoconf set it (XXautoconf) or, |
| 30 |
baselayout set it (00basic). Given what's in 00basic, I'd lean towards |
| 31 |
having autoconf set it. Unless someone else has objections, feel free |
| 32 |
to add it/set it. |
| 33 |
|
| 34 |
Fabian |
| 35 |
|
| 36 |
|
| 37 |
-- |
| 38 |
Fabian Groffen |
| 39 |
Gentoo on a different level |
Archives