From: Matt Doughty <wyndigo@zad.att.ne.jp>
To: gentoo-dev@gentoo.org
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] prefix overide portage
Date: Wed, 20 Feb 2002 16:02:37 +0900 [thread overview]
Message-ID: <20020220070237.GA3364@zad.att.ne.jp> (raw)
In-Reply-To: <87r8ngd9uf.fsf@tea.thpoon.com>
<SNIP>
>
> I, too, suggest that we introduce the functionality of the custom
> package prefix in /etc/make.conf.
> --
to me I see two logical configurable prefixes:
X11: I understand that is currently default to /usr/X11R6, and I
consider this a good default, but there is no reason to set
it in stone.
Portage packages: leaving the default to /usr is fine, but I would
really think that shouldn't become a dumping ground like it has
in so many other distros. I can understand those who don't care
can leave it in default dumping ground mode, and still allow
those of us who like a "cleaner" solution to have our way.
I personally would like to leave /bin,/sbin,/lib /usr/bin,/usr/lib,
and /usr/sbin alone after the initial bootstrap. I don't want
optional packages to intermingle in the same file space as those
that are needed for the system to function. The ability to create
a clean delineation is doing the right thing(TM) from my perspective.
I think this really ammounts to good engineering, and if the goal is
to be more flexible than the ports/pkgsrc system this is needed
functionality.
On a related note, I think it would be wise to clearly delineate
packages that are needed for basic booting system in some way. If
this functionality already exists, and I missed it please let me
know. My main thought here is I want the ability to rebuild the
base system readily. Actually the more I think of it the better it
would be if one could say bootstrap a system to test directory first
(maybe /usr/local/base-test) and then assuming a possibly even chrooting
to test the new base simply reinstall the proper place or rerun the
bootstap without the overridden directory. One way or another the
ability to override the target for a package has many practical
applications. Once again, let me know what I can do to help with this.
--Matt
next prev parent reply other threads:[~2002-02-20 7:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 14:13 [gentoo-dev] prefix overide portage Matt Doughty
2002-02-19 20:00 ` Bruce A. Locke
2002-02-20 4:38 ` Dave Lee
2002-02-20 5:02 ` Arcady Genkin
2002-02-20 7:02 ` Matt Doughty [this message]
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=20020220070237.GA3364@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