You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clyde initializes a transaction at the very beginning of sync_aur_trans, which is a lot earlier than the AUR packages are actually available. The packages are downloaded at a much later date, built, and only then installed. This means there is a long duration during which database operations can not be made.
The process looks like this:
initialize transaction
install binary packages/dependencies
find AUR packages
for each AUR package; download package, build package, install package.
release transaction
I think the process should look more like this:
download AUR packages
download AUR package sources
initialize transaction,
install dependencies
build and install AUR packages
release transaction
The AUR building step might still take a while, but it would be difficult/impossible to separate building and installing AUR packages due to build-time dependencies.
This would mean the database is not locked until required. The download step can take hours for large packages (e.g. games with lots of game data), especially with many dependencies.
Perhaps AUR dependencies can be checked prior to downloading the sources to prevent unnecessary bandwidth being used. Not sure if this already happens or not.
The text was updated successfully, but these errors were encountered:
Clyde initializes a transaction at the very beginning of sync_aur_trans, which is a lot earlier than the AUR packages are actually available. The packages are downloaded at a much later date, built, and only then installed. This means there is a long duration during which database operations can not be made.
The process looks like this:
I think the process should look more like this:
The AUR building step might still take a while, but it would be difficult/impossible to separate building and installing AUR packages due to build-time dependencies.
This would mean the database is not locked until required. The download step can take hours for large packages (e.g. games with lots of game data), especially with many dependencies.
Perhaps AUR dependencies can be checked prior to downloading the sources to prevent unnecessary bandwidth being used. Not sure if this already happens or not.
The text was updated successfully, but these errors were encountered: