[zypp-devel] Re: [softwaremgmt] Re: zypp-refresh
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. Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Michael Matz wrote:
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@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Hi, On Wed, 23 Jul 2008, Jan Kupec wrote:
(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.
Hmm. I for instance switch off auto-refresh on repos which are not always available (for instance on my laptop I have some SuSE internal repos, that can only be accessed from inside SuSE or over RAS) and would cause hanging if they were touched automatically. Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Wednesday 23 July 2008 09:37:56 am Michael Matz wrote:
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.
Hmm. I for instance switch off auto-refresh on repos which are not always available (for instance on my laptop I have some SuSE internal repos, that can only be accessed from inside SuSE or over RAS) and would cause hanging if they were touched automatically.
On the other hand Maybe the best option is to create configuration option that will start zypper in one of 2 modes, refresh all or refresh enabled only. System default might be refresh all to avoid dependency problems that many inexperienced users will run into if they disable refresh for some repositories, and forget that, while other still have ability to keep some repos on manual refresh. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Rajko M. wrote:
On the other hand
Maybe the best option is to create configuration option that will start zypper in one of 2 modes, refresh all or refresh enabled only. System default might be refresh all to avoid dependency problems that many inexperienced users will run into if they disable refresh for some repositories, and forget that, while other still have ability to keep some repos on manual refresh.
http://en.wikipedia.org/wiki/Overengineering ;-) Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Duncan Mac-Vicar Prett wrote:
Rajko M. wrote:
On the other hand Maybe the best option is to create configuration option that will start zypper in one of 2 modes, refresh all or refresh enabled only. System default might be refresh all to avoid dependency problems that many inexperienced users will run into if they disable refresh for some repositories, and forget that, while other still have ability to keep some repos on manual refresh. http://en.wikipedia.org/wiki/Overengineering ;-)
Note also, that the thread is not about zypper, but about zypp-refresh utility, which is completely independent code. j. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Thursday 24 July 2008 04:36:53 am Jan Kupec wrote:
Duncan Mac-Vicar Prett wrote:
Rajko M. wrote:
On the other hand Maybe the best option is to create configuration option that will start zypper in one of 2 modes, refresh all or refresh enabled only. System default might be refresh all to avoid dependency problems that many inexperienced users will run into if they disable refresh for some repositories, and forget that, while other still have ability to keep some repos on manual refresh.
If it would be about zypper, as I thought, it is not. Simple for new users, complicated for those that think that they handle complexity ;-)
Note also, that the thread is not about zypper, but about zypp-refresh utility, which is completely independent code.
j.
But, it is about something else :-( It is getting hard to catch with all the development, even in packaging area. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (4)
-
Duncan Mac-Vicar Prett -
Jan Kupec -
Michael Matz -
Rajko M.