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
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-dev@g.o
From: Mikael Hallendal <micke@...>
Subject: Re: hardcoded PATHS in .ebuild
Date: Mon Sep 24 06:27:02 2001
mån 2001-09-24 klockan 14.20 skrev Martin Schlemmer:
> Hi
> In hacking a few .ebuild, i noticed that most .ebuilds have paths to
> where Gnome, Mozilla, etc is hardcoded ?!?
> Now I know that it is not everyday that they change, but since the base
> location for many packages will be changed now, cant it be done
> correctly this time ?  In other words rather use defined variables that
> should be defined when the base package is installed (like KDEDIR,
> MOZILLA_FIVE_HOME, etc) since the base package should already have been
> merged when you get to subpackages ....


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

BTW. Testing your Mozilla ebuild right now.


> Some suggestions/reasons would be appreciated.
> greetings
> MS
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@g.o
Mikael Hallendal                micke@...
CodeFactory AB        
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918

Re: hardcoded PATHS in .ebuild
-- Martin Schlemmer
hardcoded PATHS in .ebuild
-- Martin Schlemmer
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
hardcoded PATHS in .ebuild
Next by thread:
Re: hardcoded PATHS in .ebuild
Previous by date:
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.