From: Brian Harring <ferringb@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Downloading while compiling - FETCHCOMMAND inside.
Date: Sun, 04 Apr 2004 06:38:00 -0500 [thread overview]
Message-ID: <1081078659.12659.1.camel@exodus> (raw)
In-Reply-To: <20040330023732.10286867.Michael.Waiblinger@web.de>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Why not check into bug 1661
(http://forums.gentoo.org/viewtopic.php?t=1661)?
Carpaski had a set of patches at
http://gentoo.twobit.net/portage/threaded/ against .36- isolating the
emerge changes shouldn't be too much, although portage.py might take a
bit more. At the very least seems like a better approach to a permenant
solution, although the age of the code might warrant just rewriting it
from scratch. Portage.py's modifications would at the very least
require updating for .49+ global var adjustments...
/me heads to bed.
~brian
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-04-04 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 13:18 [gentoo-portage-dev] emerge feature request: Downloads managed by lock file system Thomas Horsten
2004-02-07 17:04 ` Simon Mika
2004-02-07 17:17 ` Sven Vermeulen
2004-02-07 22:07 ` Jeff Smelser
2004-02-08 0:59 ` Thomas Horsten
2004-03-28 0:21 ` Roman Gaufman
2004-03-29 14:39 ` [gentoo-portage-dev] Downloading while compiling - FETCHCOMMAND inside Roman Gaufman
2004-03-29 18:10 ` Wiebel
2004-03-29 19:35 ` Roman Gaufman
2004-03-30 0:37 ` Wiebel
2004-04-04 11:38 ` Brian Harring [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=1081078659.12659.1.camel@exodus \
--to=ferringb@gentoo.org \
--cc=gentoo-portage-dev@lists.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