X-Spam-Check-By: sourceware.org Message-ID: <20060321225235.49625.qmail@web51507.mail.yahoo.com> Date: Tue, 21 Mar 2006 14:52:35 -0800 (PST) From: "James R. Phillips" Reply-To: antiskid56-cygwin AT yahoo DOT com Subject: Re: updatedb broken [attn: lapack maintainer] To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com The lapack maintainer would be me. >That's because /etc/profile.d/lapack.sh is polluting the namespace with >BINDIR=/usr/lib/lapack Hm, you are correct. This is not purposeful, but inadvertent. I did not note carefully that the script is being sourced, so that modifications to commonly used environmental variables like BINDIR are retained when the script completes. >I don't know if findutils or lapack is at fault for this conflicting >definition of what $BINDIR represents. I can probably work around it >in the next findutils release, but wonder if the lapack maintainer should >instead be more careful to not pollute the environment during its profile.d >script. lapack.sh is at fault here. It should use variable names less likely to produce collisions, perhaps prefixed with "LA_", or some similar device. I will fix this in the near future. Thanks for pointing out the issue. Jim Phillips -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/