On Mon, Nov 10, 2008 at 06:10:48AM -0500, Felix Miata wrote:
On 2008/11/10 11:55 (GMT+0100) Peter Poeml composed:
It should do the same as Yum, IMO: download metadata + packages, and when that fails at any point, you'd refresh the local metadata and start over, and once you have a consistent state on your system (including packages) _then_ start the actual update.
That can't work consistently on systems with limited / space. Most of my installs use a small / partition, so downloading all packages first can easily fill up / before installation of any packages starts. It happens to me frequently on systems using apt-get.
Yes - I actually didn't mean to imply that this should be the *only* way of doing it. An optional "download on the fly" strategy makes sense in some cases.
Smart defaults to downloading everything first, so I have to work around that with small scripts that divide the task into manageable chunks. It has a stepped option, but the first time it runs into an unavailable package, it halts instead of trying to do any other packages.
It is much easier to work around in this way than in the other.
URPMI defaults to downloading small bunches, installing them, then repeating. I like that about it, and that zypper is more like it than smart or apt-get.
I actually find myself doing that frequently because in real life there are always some issues when doing a large update that one needs to work through. But I think it is a hard to systematically separate an update in reasonable chunks, without ending up having at least one pretty large chunk. A useful distinction I often make is C and C++ programs. C++ programs are rarely vital, and I don't care if they are updated later or if the update doesn't complete. Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development