public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@saintmail.net>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] hardcoded PATHS in .ebuild
Date: Mon Sep 24 07:01:01 2001	[thread overview]
Message-ID: <1001336349.15272.18.camel@nosferatu.lan> (raw)
In-Reply-To: <1001334352.29366.8.camel@zoidberg>

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




  reply	other threads:[~2001-09-24 13:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24  6:21 [gentoo-dev] hardcoded PATHS in .ebuild Martin Schlemmer
2001-09-24  6:27 ` Mikael Hallendal
2001-09-24  7:01   ` Martin Schlemmer [this message]
2001-09-24  7:09     ` Martin Schlemmer
2001-09-24  7:16       ` Mikael Hallendal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1001336349.15272.18.camel@nosferatu.lan \
    --to=azarah@saintmail.net \
    --cc=gentoo-dev@cvs.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox