Mailinglist Archive: zypp-devel (64 mails)
| < Previous | Next > |
[zypp-devel] Re: [softwaremgmt] Re: zypp-refresh
- From: Jan Kupec <jkupec@xxxxxxx>
- Date: Wed, 23 Jul 2008 16:27:16 +0200
- Message-id: <48873FC4.5020502@xxxxxxx>
Michael Matz wrote:
The autorefresh is meant to trigger refresh when you do something for which repo data are needed, and it is not an explicit refresh call (which is meant to refresh all repos).
Which is probably the case of the updater applet. But if you call zypp-refresh on the command line, you could as well expect that it will refresh all repos.
j.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
Hi,
On Wed, 23 Jul 2008, Marcus Meissner wrote:
But this would mean adding another possibility (command argument) to the zypp-refresh-wrapper. On the other hand, the updater may be the only user of zypp-refresh, so we might as well just change it to refresh only the autorefresh-enabled repos and be done with it.I would say to only refresh the autorefresh ones, no option.
(Its what I would expect ;)
Agreed. What sense would the autorefresh setting have if it wouldn't affect automatic refreshing.
The autorefresh is meant to trigger refresh when you do something for which repo data are needed, and it is not an explicit refresh call (which is meant to refresh all repos).
Which is probably the case of the updater applet. But if you call zypp-refresh on the command line, you could as well expect that it will refresh all repos.
j.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |