Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Martin Schlemmer <azarah@...>
Subject: Re: hardcoded PATHS in .ebuild
Date: Mon Sep 24 07:01:01 2001
On Mon, 2001-09-24 at 14:25, Mikael Hallendal wrote:
> Hi!
> 
> I've brought up this issue before. The main reason for this is to be
> able to say, I want all GNOME-stuff in /usr/local/gnome instead of
> /opt/gnome (for example).
> 
> However if we decide to move everything to /usr this won't be an issue
> anymore. 
> 

I know about that issue .. not entirely what i meant.  Rather, if a app
need to use the base dir for gnome, /opt/gnome as of current, why
hardcode it into the ebuild as /opt/gnome, but not use $GNOME_PATH
instead?  If gnome need to be relocated in future, it will be much
easier ....

Greetings,
  MS



Replies:
Re: hardcoded PATHS in .ebuild
-- Martin Schlemmer
References:
hardcoded PATHS in .ebuild
-- Martin Schlemmer
Re: hardcoded PATHS in .ebuild
-- Mikael Hallendal
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: hardcoded PATHS in .ebuild
Next by thread:
Re: hardcoded PATHS in .ebuild
Previous by date:
Re: hardcoded PATHS in .ebuild
Next by date:
Re: hardcoded PATHS in .ebuild


Updated Jun 17, 2009

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.