From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2728 invoked from network); 7 Feb 2004 13:18:53 +0000 Received: from smtp.gentoo.org (128.193.0.39) by eagle.gentoo.oregonstate.edu with DES-CBC3-SHA encrypted SMTP; 7 Feb 2004 13:18:53 +0000 Received: from lists.gentoo.org ([128.193.0.34] helo=eagle.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.24) id 1ApSMG-00005G-OP for arch-gentoo-portage-dev@lists.gentoo.org; Sat, 07 Feb 2004 13:18:52 +0000 Received: (qmail 13211 invoked by uid 50004); 7 Feb 2004 13:18:51 +0000 Mailing-List: contact gentoo-portage-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-portage-dev@lists.gentoo.org X-BeenThere: gentoo-portage-dev@gentoo.org Received: (qmail 28604 invoked from network); 7 Feb 2004 13:18:51 +0000 From: Thomas Horsten To: gentoo-portage-dev@lists.gentoo.org Date: Sat, 7 Feb 2004 13:18:47 +0000 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402071318.47224.thomas@horsten.com> Subject: [gentoo-portage-dev] emerge feature request: Downloads managed by lock file system X-Archives-Salt: 4c3d7ac0-18ae-43e4-a884-2a5c6e99ec2b X-Archives-Hash: aeaf05234586574b41bb54feeaccdb1f Hi, I have a request for an emerge feature that I think would be useful for a lot of people. I have quite a fast machine with RAID and 3GHz CPU, and only a 512kbit/s Internet connection. When I do an "emerge -u world" most of the time actually goes by waiting for packages to download. For most ebuilds, It takes roughly the same time to download as to compile. So to speed up my builds, I usually start an "emerge -f -u world". Once the first couple of packages have downloaded I then start an "emerge -u world" in another shell. This works great as long as the fetcher process is ahead of the builder process. But if some packages are built too quickly, the builder process catches up. It then starts downloading the same file as the downloader process, resuming from wherever the downloader had gotten to, so now two downloaders are writing to the same file (waste of bandwidth and a possible source of corrupted archives). What I suggest is that emerge will put a lockfile in place when it's downloading a file, eg. "name-of-package.tar.bz2.lock", or by using fcntl locks. Then if the "builder" catches up, and finds the output file is already open, it waits on the lock for the download to complete and then continues unpacking after that. I already love gentoo and the portage system, it's by far the best available, but adding this feature would make it even better IMHO. Regards, Thomas -- gentoo-portage-dev@gentoo.org mailing list