Mailinglist Archive: opensuse-bugs (7187 mails)
| < Previous | Next > |
[Bug 356741] zypper search without refreshing should be possible
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 29 Jan 2008 02:09:22 -0700 (MST)
- Message-id: <20080129090922.46A4524538D@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=356741
User jkupec@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=356741#c3
Ján Kupec <jkupec@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Normal |Enhancement
Status|NEW |ASSIGNED
--- Comment #3 from Ján Kupec <jkupec@xxxxxxxxxx> 2008-01-29 02:09:21 MST ---
(In reply to comment #2 from Adrian Schröter)
This is partly a matter of taste and a matter of our policy, rest assured we
have thought about this. The general agreement to date is that the primary
focus is the stable release and its repository + update repository. The stable
repo does not change (but eventually can) so the autorefresh does not hurt. As
for the update repo, it is quite important to have it always up to date and it
is much smaller and quicker to refresh than full distro repo. This is the most
important use case.
The rest of the use cases are completely up to the user who can add any repos
he or she likes. After adding the repo (and also in the repo list) the status
of the autorefresh is shown, so the user knows about it. He can turn it on or
of, he can even add the repo with autorefresh disabled with a special option. I
believe we also agreed that these use cases are for those more advanced, who
are able to figure out that there is a thing called autorefresh and decided
whether to turn it on or off. Ordinary users, on the other hand, are better off
with the autorefresh enabled, so they are not surprised by a 'can't find
foo-x.x.x.rpm' message.
As for this bug report, i agree the --dont-autorefresh option would be handy.
--
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.
User jkupec@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=356741#c3
Ján Kupec <jkupec@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Normal |Enhancement
Status|NEW |ASSIGNED
--- Comment #3 from Ján Kupec <jkupec@xxxxxxxxxx> 2008-01-29 02:09:21 MST ---
(In reply to comment #2 from Adrian Schröter)
hm, did you ever discussed to go the apt way and distinguish between upgrade
and update ?
This means update/install/search/.. would not call a refresh by default but
simply fail when the file is not on the server and offer the user to update
meta data than ?
Or we may should not default to autorefresh anymore, but handle the case, if
something fails better ?
This is partly a matter of taste and a matter of our policy, rest assured we
have thought about this. The general agreement to date is that the primary
focus is the stable release and its repository + update repository. The stable
repo does not change (but eventually can) so the autorefresh does not hurt. As
for the update repo, it is quite important to have it always up to date and it
is much smaller and quicker to refresh than full distro repo. This is the most
important use case.
The rest of the use cases are completely up to the user who can add any repos
he or she likes. After adding the repo (and also in the repo list) the status
of the autorefresh is shown, so the user knows about it. He can turn it on or
of, he can even add the repo with autorefresh disabled with a special option. I
believe we also agreed that these use cases are for those more advanced, who
are able to figure out that there is a thing called autorefresh and decided
whether to turn it on or off. Ordinary users, on the other hand, are better off
with the autorefresh enabled, so they are not surprised by a 'can't find
foo-x.x.x.rpm' message.
As for this bug report, i agree the --dont-autorefresh option would be handy.
--
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.
| < Previous | Next > |