public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Doughty <wyndigo@zad.att.ne.jp>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] prefix overide portage
Date: Tue, 19 Feb 2002 23:13:51 +0900	[thread overview]
Message-ID: <20020219141351.GC2375@zad.att.ne.jp> (raw)

Hi,
I hate to start by complaining or critisizing what I consider a
wonderful project.  I'm basically a NetBSD user who is looking
for functionality(hardware 3d support) that linux has, and 
NetBSD is lacking. I was working through the install, and ran
into a couple oddities/annoyances.  I noticed that alot of
packages in portage statically set the install prefix.  I find
this to be very undesirable behavior, and was wondering if
this is temporary or has noone complained about this rather
rigid structure? From my perspective a system should be divided 
in this manner:

base system (kernel, and userland): 	--prefix=/, and --prefix=/usr
package system installed pkgs:     	--prefix=/usr/pkg
X system:			 	--prefix=/usr/X11R6

this leaves /usr/local, and /opt for hand built packages. In NetBSD
the base system is completely seperate from the package system, and
the package system, and X prefixes can be overridden by the 
enviroment variables LOCALBASE, and X11BASE respectively. I love 
the overall design of the system, and clean nature of the /etc
directory.  I would be happy to help make the needed changes to
allow for this increased flexibility.

--Matt


             reply	other threads:[~2002-02-19 14:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19 14:13 Matt Doughty [this message]
2002-02-19 20:00 ` [gentoo-dev] prefix overide portage Bruce A. Locke
2002-02-20  4:38   ` Dave Lee
2002-02-20  5:02     ` Arcady Genkin
2002-02-20  7:02       ` Matt Doughty
2002-02-20 10:07         ` Bruce A. Locke
2002-02-20 10:18           ` Gert Menke
2002-02-21  0:46           ` Matt Doughty
2002-02-20  7:15       ` Daniel Robbins
2002-02-20 15:41         ` Dave Lee
2002-02-20  9:53     ` Bruce A. Locke

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=20020219141351.GC2375@zad.att.ne.jp \
    --to=wyndigo@zad.att.ne.jp \
    --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