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 <gentoo-dev@g.o>
From: Martin Schlemmer <azarah@...>
Subject: hardcoded PATHS in .ebuild
Date: Mon Sep 24 06:21:01 2001
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 ....

Some suggestions/reasons would be appreciated.

greetings
MS





Replies:
Re: hardcoded PATHS in .ebuild
-- Mikael Hallendal
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Mozilla non-root execution hopefully resolved (mozilla-0.9.4-r1.ebuild)
Next by thread:
Re: hardcoded PATHS in .ebuild
Previous by date:
Mozilla non-root execution hopefully resolved (mozilla-0.9.4-r1.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.