From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DMARC_NONE,FREEMAIL_FROM, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from apex.matrix.net (1.pool2.ftthtokyo.att.ne.jp [165.76.218.1]) by chiba.3jane.net (Postfix) with ESMTP id 51F05200A996 for ; Wed, 20 Feb 2002 01:04:37 -0600 (CST) Received: by apex.matrix.net (Postfix, from userid 1003) id CC3DC7E1A; Wed, 20 Feb 2002 16:02:37 +0900 (JST) Date: Wed, 20 Feb 2002 16:02:37 +0900 From: Matt Doughty To: gentoo-dev@gentoo.org Cc: gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] prefix overide portage Message-ID: <20020220070237.GA3364@zad.att.ne.jp> References: <87r8ngd9uf.fsf@tea.thpoon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87r8ngd9uf.fsf@tea.thpoon.com> User-Agent: Mutt/1.3.27i Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 5c90f6b9-af46-4323-aeec-a52da122929f X-Archives-Hash: 4f2f1a1dbaedc3082d61afab0d640214 > > 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