On 5/27/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
> On 5/27/07, Dan Nicholson <[EMAIL PROTECTED]> wrote:
>
> > It might just be best to drop the globbing altogether and assume that
> > if you install something in /opt, then you will setup the appropriate
> > PATH, PKG_CONFIG_PATH, ld.so.conf, etc. In that case, we can just have
> > a single test for /opt/bin and /opt/lib/pkgconfig just like the
> > /usr/local cases.
>
> What I have is:
>
> #for directory in $(find /opt/*/lib/pkgconfig -type d 2>/dev/null); do
> # pathappend $directory PKG_CONFIG_PATH
> #done
Right, so I think we agree here that the globbing should just be
dropped. It's more consistent with the book, too, since we say
"remember to add ... to the PATH, PKG_CONFIG_PATH, etc.". You might
see things twice we the globbing.
Although, I think we should leave in
if [ -d /opt/bin ]; then
pathappend /opt/bin
fi
if [ -d /opt/lib/pkgconfig ]; then
pathappend /opt/lib/pkgconfig PKG_CONFIG_PATH
fi
In case anyone wants to make use of these directories.
> if [ -d /opt/qt/lib/pkgconfig ] ; then
> pathappend /opt/qt/lib/pkgconfig PKG_CONFIG_PATH
> fi
>
> if [ -d /opt/kde/lib/pkgconfig ] ; then
> pathappend /opt/kde/lib/pkgconfig PKG_CONFIG_PATH
> fi
Could these be better in their own script? I.e., /etc/profile.d/qt.sh?
I suppose it's up to the user where they put these settings.
So, do you agree that the globbing should be dropped, but that we
should leave paths for /opt/bin and /opt/lib/pkgconfig?
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
