-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Basil Chupin wrote:

Jan Kupec wrote:

...

Basil Chupin wrote:

...

Are you sure that you are talking about /var/cache/ZYPPER and not ZYPP because I do not have a cache called zypper on my system. That is because you did not install an rpm file with zypper so far. Like 'zypper in foo.rpm'.

So you are specifically talking about using zypper from the command line, and not zypper as from YaST, right?

Yast does not use zypper, it uses libzypp, the library which powers both yast and zypper. So yes, i am talking about zypper, the command line tool.

...

The good thing about this cache is, that anything you install this way, will be there, even remote rpms, like in 'zypper install http://download.foo.org/rpms/the.rpm'

I prefer to use smart to maintain my system - although at the moment I use both zypper and smart. With smart I know where the rpms go, and if

With zypp-based apps, they go to /var/cache/zypp/packages/<repoalias>/..., if keeppackages attribute is set in the repository's .repo file. If it is not, no .rpms are cached. The only exception is when you install an _rpm file_ directly with zypper, then the rpms go to /var/cache/zypper/RPMS. Note that this is different than 'zypper in packagename'. It is 'zypper in rpm_file_path_or_url.rpm'.

there is a hassle with dependencies I can use "rpm -Uvh *rpm --test" to find the problems and remove the 'offending' rpms before finally running "rpm -Uvh *rpm".

Hm... hassle with dependencies? I don't remember i ever needed to do something like this with zypper/yast. What kind of hassle do you mean?

Another reason why I prefer smart to zypper is that smart downloads the rpms but does not apply them until all are downloaded.

We are currently working on this. See e.g. http://en.opensuse.org/Libzypp/Refactoring/Commit

zypper on the other hand applies each rpm as it is downloaded so that should the connection to the internet be lost and power to the computer is lost as well then the whole dependency lattice is lost and a reboot will most probably leave me with an unbootable/unusable system.

It is not that bad since it installs the rpms in correct order, so unless the cut happened when installing some circular dependencies, the dependency tree would not break. - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkl5nCgACgkQgEhGpmN+6QG12ACghossZ7a5SCDZqSOgbmT+lPpQ nSwAn1ubGDUxf7ADqUqCenMs/w7x+Tva =3+x0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org