From: Jack Morgan <jmorgan@gentoo.org>
To: gentoo-dev@gentoo.org
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] installing portage in another directory structure
Date: Tue, 20 May 2003 08:09:19 -0700 [thread overview]
Message-ID: <20030520150919.GA7477@takao> (raw)
In-Reply-To: <200305201635.57663.sh@kde-coder.de>
On Tue, May 20, 2003 at 04:35:57PM +0200, Stephan Hermann wrote:
>
> just thinking about portage and thinking about using it to build up a
> dedicated software build server.
>
> As I saw portage want a hardcoded structure for config files etc. (e.g. /etc
> /usr/portage/...).
>
> I'm not the best python programmer, but can I replace all hardcoded
> directories to configurable entries ?
Edit /etc/make.conf... here is part you want to look at...
# PORTDIR is the location of the portage tree. This is the repository
# for all profile information as well as all ebuilds. This directory
# itself can reach 200M. WE DO NOT RECOMMEND that you change this.
#PORTDIR=/usr/portage
Cheers,
Jack Morgan
Gentoo/Sparc
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-05-20 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 14:35 [gentoo-dev] installing portage in another directory structure Stephan Hermann
2003-05-20 14:36 ` Sven Vermeulen
2003-05-20 14:54 ` Stephan Hermann
2003-05-20 19:24 ` Paul de Vrieze
2003-05-20 20:30 ` Martin Schlemmer
2003-05-20 20:46 ` Paul de Vrieze
2003-05-20 21:15 ` Martin Schlemmer
2003-05-20 21:49 ` George Shapovalov
2003-05-21 0:22 ` Luke-Jr
2003-05-21 3:35 ` Stephan Hermann
2003-05-21 9:20 ` Paul de Vrieze
2003-05-21 11:55 ` Stephan Hermann
2003-05-20 15:09 ` Jack Morgan [this message]
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=20030520150919.GA7477@takao \
--to=jmorgan@gentoo.org \
--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