Mailinglist Archive: zypp-devel (92 mails)
| < Previous | Next > |
[zypp-devel] option repo.add.probe and repo enablement
- From: Duncan Mac-Vicar Prett <dmacvicar@xxxxxxx>
- Date: Fri, 3 Aug 2007 17:51:15 +0200
- Message-id: <200708031751.18677.dmacvicar@xxxxxxx>
I just changed the way repositories are added.
Before, zypper probed the repositories in case the --type option was not
given, and then always tried to give ZYpp a valid type.
However ZYpp also did some probing, so I removed all ZYpper related code. How
does it work now?
- If type is given, the repository is added and the given type is used.
- If zypp.conf repo.add.probe is enabled, the repository is probed either type
is given or not
- If type is not given the repository is probed no matter if repo.add.probe is
off.
- if you want to avoid network access completely, always specify the type when
adding and set repo.probe.url to 0
- if you want avoid network access when not needed, set repo.probe.url to off,
then network will be accessed only if the repository type is unknown.
- If you want to always check, set repo.probe.url to 1
Also, zypper autorefresh and enabled options are fixed so the priority is:
- what you specified in the command line
- the .repo file you are adding
- libzypp defaults
--
Duncan Mac-Vicar Prett
Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |