public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Amiel Martin <martina3@cc.wwu.edu>
To: "Kurt V. Hindenburg" <khindenburg@cherrynebula.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Multiple DISTDIR
Date: Sun, 18 May 2003 00:54:50 -0700 (PDT)	[thread overview]
Message-ID: <Pine.GSO.4.21.0305180054370.19681-100000@titan.cc.wwu.edu> (raw)
In-Reply-To: <200305171707.44197.khindenburg@cherrynebula.net>

comments? great idea

-AMiel

On Sat, 17 May 2003, Kurt V. Hindenburg wrote:

I've patch portage.py (VERSION="2.0.47-r10") and ebuild.sh to use a 
new variable in make.conf.  The new variable is DISTDIRS="directory1 
directory2 etc".
The purpose of this is to allow people to have distfiles in multiple 
locations (ie. cdrom, nfs, etc).

What happens:
1. Look in DISTDIR for files (as normal)
2. If not found, traverse through all directories in DISTDIRS looking 
for files.
3. Set a new environment variable (DDIR) pointing to correct directory 
holding the files.
4. ebuild.sh will use DDIR if set instead of DISTDIR.

Notes:
1. I couldn't really figure out what the envirnoment variables A and 
AA were meant for.

2. I thought it best to avoid messing with the envirnoment variable 
DISTDIR to avoid confusion/problems (hence the new DDIR).

3. How can I get the latest cvs copy of portage as I would assume 
people would want a diff against that.

This will need further testing/fixing as I've only spent a few hours 
on it and I'm a non-python user.

Anyone doing something like this or anyone have any comments?

 Kurt
---
  There is no good and evil; there is only power.

--
gentoo-dev@gentoo.org mailing list


--
gentoo-dev@gentoo.org mailing list


      parent reply	other threads:[~2003-05-18  7:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 22:07 [gentoo-dev] Multiple DISTDIR Kurt V. Hindenburg
2003-05-17 22:48 ` Robin H.Johnson
2003-05-18  5:08   ` Georgi Georgiev
2003-05-18  5:18     ` Jon Portnoy
2003-05-18  7:54 ` Amiel Martin [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=Pine.GSO.4.21.0305180054370.19681-100000@titan.cc.wwu.edu \
    --to=martina3@cc.wwu.edu \
    --cc=gentoo-dev@gentoo.org \
    --cc=khindenburg@cherrynebula.net \
    /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