Cristian Morales Vega wrote:

2009/5/25 Michael Andres :

...

On Friday 22 May 2009 18:03:29 Jano Kupec wrote:

...

...

I have 2 questions for libzypp and the zypper commandline tool:

1. Is there any way to completely and forcefully disable the vendor check ? I now that I can add trusted vendors to the list, but that is not my objective. I rely on the repo priority, and do not wish to use the vendor check feature of libzypp. None that i know of. CCing to zypp-devel mailing list. We can have a zypp.conf option for this. That should not be a big deal.

Any news about the plugin system?

Which plugin system?

That should allow to change all these options, shouldn't? Looking into the log there are a lot of options, I'm not sure about the meaning of some of them:

fixsystem = 0 allowdowngrade = 1 allowarchchange = 1 allowvendorchange = 1 allowuninstall = 0 updatesystem = 1 allowvirtualconflicts = 0 noupdateprovide = 0 dosplitprovides = 1 onlyRequires = 0 ignorealreadyrecommended = 0 distupgrade = 1 distupgrade_removeunsupported = 0

These are solver settings and are either configurable via zypp.conf, or passed to libzypp/satsolver by UIs according to commands the user does. E.g. updatesystem = 1 is set by 'zypper up', onlyRequires is set in zypp.conf, or by 'zypper <command> --no-recommends', etc. Some of them are not exposed to UIs yet. If you're curious about some particular things you see in the logs, just ask. They're not always really understandable for a casual observer (in fact sometimes it would help to make them more understandable) :O)

Each user wants something different. Using zypper since 11.0, what I miss the most right now is a dist-upgrade *with* vendor check (or an update allowing downgrades). Why? Well, the KDE OBS repos sometimes (...frequently!!) have updates with a lower version-release number. To update to the latest packages I need an update method that allows downgrades, dist-upgrade does it just fine... but, since it ignores the vendor, at the same time it updates my KDE it also changes my Packman K3B package for other without MP3 support (plus the more esoteric libsndfile case from bug #500407).

...

...

...

2. 'Download first - install after' behavior. I remember someone mentioning a 'secret' unsupported option or configuration for zypp to start installation, only after/if all packages have been downloaded first. I just don't remember what it was. We will have better support for this in the next release. 'Download first' or 'Download only' will be doable without a bunch of cryptic options.

When 'Download first', will a file colision check be done before starting the installation? (rpm without --replacefiles). It would be something good to have... but would also mean one method would allow installations the other would not.

-- 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)---