https://bugzilla.novell.com/show_bug.cgi?id=887188 https://bugzilla.novell.com/show_bug.cgi?id=887188#c2 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #2 from Michael Andres <ma@suse.com> 2014-07-15 13:43:14 CEST ---
Bugs: 1. "-C" command line option has no effect a. Similarly, "--raw-cache-dir" has no effect either
Yes, this was fixed in zypper-1.4.4. Zypper mistook the way the underlying libzypp organizes it's chache dirs. That's why the options are not usable for your purpose on SLE11.1. '-C,--cache-dir' fails to redirect the complete cache tree. '--raw-cache-dir' (copy of the original repo metada) works, but it does not help you because repo2solv.sh will parse these data and create a .solv-file cache for fast access in (/var/cache/zypp)/solv. A --solv-cache-dir option to redirect this directory as well is missing.
2. Adding "cachedir" setting to "~/.zypper.conf" has no effect 3. Authoring own "zypp.conf" and supplying via "--config" has no effect
That's right. zypper, YaST, PackageKit all use a common package management library (libzypp) and it's options (e.g. the cache dirs) are kept in zypp.conf. zyppers --config option affects only it's own config file (zypper.conf), and this file is not meant to override the common zypp.conf options. _____WORKAROUND: SLE11.1 is out of maintenance, so I can't offer an official zypper fix for this, but: - libzypp itself supports redirecting it's "zypp.conf" via an environment variable: export ZYPP_CONF="<location (absolute path!) of your private zypp.conf>" zypper .... - I fixed at least the zypper source code to redirect the whole cache tree with -C. The patch is availabe at 'https://github.com/openSUSE/zypper/commit/cd73b1256e23ade8efdfcf499337863d27...'. (SuSE-Code-11_2-Branch is the branch for SLE11-SP1). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.