env-update produces /etc/prelink.conf among other configuration files. Sometimes, you want to ban prelinking specific directory. You have to alternatives: Either modify LDPATH in some installed file, OR add PRELINK_PATH_MASK to something like /etc/env.d/99zzzzz. I believe the latter one is preferred. However, when you set PRELINK_PATH_MASK to the exact path that is set in LDPATH earlier (usually in "alphabetically earlier" file), env-update produces both -b and -h in /etc/prelink.conf. Only the -b ("ban") option should appear there, I think. Moreover, it sometimes work -- when you set PRELINK_PATH_MASK to a parent directory of the one in LDPATH, -h is supressed, only -b shows up. This makes me think that env-update *is meant* to care. Reproducible: Always Steps to Reproduce: 1. Put the following lines into /etc/env.d/99zzzzz: LDPATH="/a/b:/c/d" PRELINK_PATH_MASK="/a:/c/d" 2. Run env-update. Actual Results: In /etc/prelink.conf you can now also find: -h /c/d -b /a -b /c/d Expected Results: "-h /c/d" from the example should not appear in /etc/prelink.conf . It does not make sense to have both -h and -b for the same directories there. Portage 2.0.51-r15 (default-linux/x86/2004.0, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.10-ck5-rudo i686) ================================================================= System uname: 2.6.10-ck5-rudo i686 AMD Athlon(TM) XP 1800+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.2.3-r5,dev-lang/python-2.3.4 [2.3.4 (#1, Oct 17 2004, 03:41:35)] dev-lang/python: 2.2.3-r5, 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r3 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -mcpu=athlon-xp -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /sbin /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -mcpu=athlon-xp -O2 -pipe -fomit-frame-pointer" FEATURES="autoaddcvs autoconfig ccache distlocks notitles sandbox sfperms userpriv" USE="x86 3dnow 3dnowex X aalib alsa apm arts berkdb bitmap-fonts caps cdparanoia cdr crypt cscope cups curl dga doc dvd dvdread encode faad fam flac font-server foomaticdb gd gdbm gif gpm imagemagick imlib ipv6 java jpeg kde lcms libcaca libg++ libwww maildir mbox memlimit mikmod mmx mmx2 mng mpeg ncurses nls nocardbus nptl oggvorbis opengl oss pam pdflib perl physfs pic png ppds pwdb python qt quicktime readline samba scanner sdl slang speex spell sse ssl tcpd tetex theora tiff truetype truetype-fonts type1-fonts unicode usb xml xml2 xmms xv xvid zlib linguas_sk linguas_cs" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS
Created attachment 49896 [details, diff] prelink_path_mask.patch Does this patch fix it?
Yes, indeed. I see it is already applied to current portage. Closing the bug.
