Lukas Ocilka wrote:
Josef Reidinger wrote:
Lukas Ocilka wrote:
Stephan Kulow wrote:
You confuse use-cases. Other people want zypper to behave like smart: download all packages and then install in one transaction. Josef's hack only does the first part :)
OK, I was actually writing about the use-case from FATE and bugzilla and mailing-lists where users want exactly this ;)
Yes, for zypper, this might work ... but does it make sense to implement code that couldn't be reused? In the times of libzypp :)?
L.
It can be reused, it is dry run policy in commit in libzypp. Only keepPackages must be allowed to don't delete downloaded files after fake install.
I'm adraid this doesn't work for installation with limited resources (memory, disk space), by default all sources during installation se keep_packages=false (please, remember the bug we had recently in installation).
And moreover downloading and installing in threads is faster than first downloading and then installing. And this is what our users want too.
L.
If everything work good this is not hard. In commit code it is separated, only we need instead providing file when needed, provide it to queue (producer and consumer) and install when queue is not empty. But if something happen what to do? Do we expect more then one failure (because download and install can both cause fail), also I am now sure if libzypp is prepared for multithread aplication. Also we must provide two progress, one for download and one for installation. Does YaST expect multithread libzypp? E.g. one callback is called and what happen if another is called and YaST still does work on first? Pepa Pepa -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org