From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11940 invoked by uid 1002); 21 May 2003 19:54:01 -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 30475 invoked from network); 21 May 2003 19:54:01 -0000 Date: Wed, 21 May 2003 14:54:01 -0500 (CDT) From: John To: gentoo-dev@gentoo.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [gentoo-dev] ebuild: Hard coded paths X-Archives-Salt: f7558cfb-5d0d-4a49-971e-66d0a5003c64 X-Archives-Hash: 836ab18f3764d07e97f8f474b0c60a09 Hello, I am attempting to create an ebuild for ircd-hybrid. This irc server requires that the path to where it is installed get compiled into the binary. I have verified that $P does not cut it (it is the location of the temorary image directory). How is something like this handled in portage? Can I know during the build where the final destination will be? Should I just "hard code" what is probably the typical case? Thanks, John -- gentoo-dev@gentoo.org mailing list