From: Sean Mitchell <SMitchell@phoenix-interactive.com>
To: "'gentoo-dev@gentoo.org'" <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] Prefixed Emerge's
Date: Wed, 17 Apr 2002 10:44:08 -0400 [thread overview]
Message-ID: <23DFAA462CC6A64487613B0E242D9FF706EC20@mercury.phoenix-interactive.com> (raw)
> A lot of ebuilds are written with the premise that the stuff goes into
> /usr, and have it hard coded. :( Even if portage starts supporting
> custom prefixes, a huge ebuild cleanup effort would be required, as
> far as I understand.
What's the alternative to something like
make prefix=${D}/usr mandir=${D}/usr/share/man install || die
then? Is there a better way?
Sean
next reply other threads:[~2002-04-17 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 14:44 Sean Mitchell [this message]
2002-04-17 14:47 ` [gentoo-dev] Prefixed Emerge's Jared H. Hudson
-- strict thread matches above, loose matches on Subject: below --
2002-04-17 14:53 Sean Mitchell
2002-04-17 15:00 ` Jared H. Hudson
2002-04-17 18:36 ` Paul de Vrieze
2002-04-16 19:06 Adam Voigt
2002-04-16 19:30 ` Paul de Vrieze
2002-04-16 21:44 ` Arcady Genkin
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=23DFAA462CC6A64487613B0E242D9FF706EC20@mercury.phoenix-interactive.com \
--to=smitchell@phoenix-interactive.com \
--cc=gentoo-dev@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