From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26707 invoked by uid 1002); 11 Sep 2003 17:14:43 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 2196 invoked from network); 11 Sep 2003 17:14:43 -0000 From: Simon Reynolds To: Jeff Griffiths Cc: "Gentoo-Dev (E-mail)" In-Reply-To: <9CE5DB8B868DCA4FB1AB629707F01DE4313EA5@exchange.activestate.ca> References: <9CE5DB8B868DCA4FB1AB629707F01DE4313EA5@exchange.activestate.ca> Content-Type: text/plain Message-Id: <1063300453.3370.93.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 11 Sep 2003 13:14:13 -0400 Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] MOZILLA_FIVE_HOME X-Archives-Salt: fd59f549-609a-4bb2-92d3-cc85dd1087d2 X-Archives-Hash: 19f6b3171238c9cdf754a3e60fc0590d On Thu, 2003-09-11 at 11:31, Jeff Griffiths wrote: > why is MOZILLA_FIVE_HOME permanently set in gentoo? > > why on gentoo is MOZILLA_FIVE_HOME permanently set? this isn't set by > for example binaries from mozilla.org, which plays nice with Komodo > > workaround is either: > % unset MOZILLA_FIVE_HOME && komodo Continuing in the same vein as this work-around, you could move komodo off your path or rename it komodo.bin or some such and create a simple sh wrapper that unsets MOZILLA_FIVE_HOME and then runs the binary. Considering that there are exist such simple and effective work-arounds, I am really surprised by the highly upset tone of your email. I hope this helps! ~Simon Reynolds -- gentoo-dev@gentoo.org mailing list