13 Apr
2013
13 Apr
'13
2:17 a.m.
On Fri, Apr 12, 2013 at 9:40 PM, Anatol Pomozov <anatol.pomozov@gmail.com> wrote: > Hi > > On Thu, Apr 11, 2013 at 11:11 PM, Allan McRae <allan@archlinux.org> wrote: >> The 4.2 roadmap is empty! >> https://wiki.archlinux.org/index.php?title=DeveloperWiki:Pacman_Roadmap >> >> I thought it would be good to discuss what people are planning. So far >> things I know are being or will be worked on: >> >> - Remove of support for PKGBUILDs with only a build() function >> - Removal of directory symlink support >> >> >> Other things that have starts of patchsets available: >> >> - Parallel operations (I think I will take this...) > Are you talking about paralleling CPU extensive operations like > integrity checking or you mean parallel in broad sense? Things I keep > in mind are: > - download package index (list) with multiple threads > - download packages in multiple threads > - install packages in parallel > - parallelize package download and installation. pacman does not > need to wait all package downloads, does it? Download is a network > bound task and installation is disk bound so doing these things in the > same time should reduce total installation time. > I think the download and installation steps should be separate from each other. What happens if the network connection is dropped while packages are still downloading after package installation has started? How would pacman's output handle simultaneous downloading and installing without making things really cluttered and difficult to read? Jason