From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] emerge feature request: Downloads managed by lock file system
Date: Sat, 7 Feb 2004 18:17:57 +0100 [thread overview]
Message-ID: <20040207171757.GA16817@gentoo.org> (raw)
In-Reply-To: <20040207170418.GA558@hx.se>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
On Sat, Feb 07, 2004 at 06:04:18PM +0100, Simon Mika wrote:
> Although I have a computer that is a bit slower I have the similiar problem.
> Downloading does not consume much processorpower and athor machine
> resources. But compiling does need a lot. Wy don't use always use 2
> parallell processes, one that downloads, and one that compiles. The
> compiling process would still need to be synced with the downloading, but
> that should not be too hard to implement with some semaphore or similiar
> solution.
A quick 'n dirty hack in the FETCHCOMMAND should suffice. Something along the
lines of (pseudocode):
FETCHCOMMAND="if exists \${DISTDIR}/`basename \${URL}.lck`; then skip; else \
touch \${DISTDIR}/`basename \${URL}.lck`; \
/usr/bin/wget ...; \
rm \${DISTDIR}/`basename \${URL}.lck`; fi"
This of course as a temporary solution ;)
Wkr,
Sven Vermeulen
--
FOSDEM 2004 Free and Open Source Developers European Meeting
21 - 22 februari Brussels, Belgium http://www.fosdem.org
http://www.gentoo.org Documentation & PR swift@gentoo.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-07 17:18 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 [this message]
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
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=20040207171757.GA16817@gentoo.org \
--to=swift@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