Re: does aptitude really need to lock the status database when downloading?
On Fri, Feb 4, 2011 at 01:10, Stanislav Maslovski
<stanislav.maslovski@gmail.com> wrote:
> For example, I am running an update on a slow connection and want to
> uninstall or install with dpkg a few packages while the others are
> being downloaded. Should not this be possible? I understand that there
> can be a situation that a dependency could be affected by such an
> action, but is not it easy to check for this right before unpacking?
As always, the (small) APT team is happy to apply well crafted patches.
(and i am sure that is true for aptitude as well)
The usecase is so small that until now nobody cared to jump through
the holes to ensure that the calculation done before the download is
still valid after the download and if not recalculate it.
So feel free to tackle it. :)
Remember that a recalculation will require to check that nothing is changed
in regards to the dependency tree: If we would need to use another path
we also install/remove other packages so we need to re-ask if the
solution is okay, downloading again, recalculating, …
Which breaks the user-interface as nobody (no user and no program)
expects a second (and third and so on) question round.
But beside that: Yes, it is easy.
Workarounds were already presented, so i just want to add that you can
also disable locking completely with Debug::NoLocking in apt-get
(i guess aptitude accepts it also, but i haven't test it)
if you are feeling *extremely* lucky…
Best regards
David Kalnischkies
Reply to: