[pacman-dev] Big pause with "pacman -R <pkg>"
Anyone else seeing a massive pause when using "pacman -R" with the latest git? Just as the progress bar starts? Allan
On Thu, Feb 28, 2013 at 12:23:27AM +1000, Allan McRae wrote:
Anyone else seeing a massive pause when using "pacman -R" with the latest git? Just as the progress bar starts?
Allan
Works for me, with the caveat that I'm running a build based on your latest working branch plus my repo-usage patches. Not sure what would be hanging here. d
On Wed, 27 Feb 2013 10:04:35 -0500 Dave Reisner <d@falconindy.com> wrote:
On Thu, Feb 28, 2013 at 12:23:27AM +1000, Allan McRae wrote:
Anyone else seeing a massive pause when using "pacman -R" with the latest git? Just as the progress bar starts?
Allan
Works for me, with the caveat that I'm running a build based on your latest working branch plus my repo-usage patches.
Not sure what would be hanging here.
d
I get a significant delay when removing a package that is the sole owner of a directory as the filelists for all installed packages are resolved to make sure none of them own the directory as well. Andrew
On 28/02/13 07:08, Andrew Gregory wrote:
I get a significant delay when removing a package that is the sole owner of a directory as the filelists for all installed packages are resolved to make sure none of them own the directory as well.
Bingo! Lets kill that... And by that I mean the resolving part for the remove (if possible). That check is to make sure that no package owns the empty directory before removing it. So if a package has files there due to a symlink, all will be fine (not empty). The case of having a symlink to a empty directory that needs kept can stay as a "bug" to avoid that massive slow-down. Allan
On Thu, Feb 28, 2013 at 6:20 AM, Allan McRae <allan@archlinux.org> wrote:
On 28/02/13 07:08, Andrew Gregory wrote:
I get a significant delay when removing a package that is the sole owner of a directory as the filelists for all installed packages are resolved to make sure none of them own the directory as well.
Bingo!
Lets kill that... And by that I mean the resolving part for the remove (if possible).
That check is to make sure that no package owns the empty directory before removing it. So if a package has files there due to a symlink, all will be fine (not empty). The case of having a symlink to a empty directory that needs kept can stay as a "bug" to avoid that massive slow-down.
I think this is why I was hesitant to add ownership checks in the remove path before. Does sound like there are some fairly common paths that can be optimized though to make this less painful. -Dan
participants (4)
-
Allan McRae
-
Andrew Gregory
-
Dan McGee
-
Dave Reisner