In openSUSE 11.0, YaST would perform installation or removal of packages and having done so would put up a dialog box asking the user if they would like to Install or remove more packages?.
In openSUSE 11.1, YaST software management simply exits without offering the aforementioned prompt.
This is irritating because I like to keep the software manager available when building from source, because tracking down the missing libraries and headers can require several iterations of “./configure”.
PS Apologies if some think this is better in “applications” but I think it’s “install” related.
It’s actually great ( i don’t have to think about closing it when set for installing something)
Problem can be solved simply by opening YaST
And when You install something, then install once but good
Solution: just keep YaST opened
HA!! I thought the same thing
I thought how could they F**K UP such simple thing and hoped that they’ll fix it until 11.1. For me it’s also some sort of a security fix, when You install You are logged with it as root, it finishes installing it finishes running as root. It’s a good practice
Say You have to go somewhere while it’s still installing, someone could have compromise Your PC if there was a security flaw
Where is the evidence that a majority wanted the option removed?
As for the security argument, it’s a tortured one that I suspect exists to justify a preference. Either you sit at your terminal or you don’t, and if you don’t you lock it. That’s as secure as it needs to be.
> how could they F**K UP such simple thing
While I might disagree with the YaST choices, it’s bang out of order to be rude about them. This isn’t a simple thing at all, it’s about striking a balance across all your users.
The other thing about repeatedly restarting every time is that the repos are repeatedly refreshed
Exactly! And if you have a lot of repos added… boy, oh boy…
Maybe a compromise would be to add a dialog at the start of software manager, that would ask if you want to refresh repos or use the cached data. That would satisfy everybody.
P.S. I know you could set that in “Software Repositories” module, but this would be so much faster, especially if you have a lot of repos to toggle (automatically refresh) on/off.
Actually, if I’m not mistaken, every time Software Management is restarted the repositories are not refreshed. The repo’s are cached, and upon restart the repo is checked to see if the cache needs to be flushed/refreshed. Only if the repo has changed will the cache be refreshed for that repo. I have ~20 repo’s configured and, once all the caches are refreshed as required, a restart takes just a few seconds.
I agree that this was not a good design decision (and i’d very much like to know how they figure that a majority supports it) An issue has been filed on it but it seems unlikely that changes will be made. Still, it can’t hurt to comment/vote.
According to that “bug” report, the dev’s were responding to previously filed “bugs” complaining about it. I’m sympathetic to the dev’s plight; they are dmd if they do, dmd if they don’t. Now that package mgmt is so fast and the caches are refreshed only if the repo changes, it’s all of a single-click and few seconds to restart the program. IMHO, this is really trivial and there are much, much more important issues to argue about.
It’s not an argument. Some users who, having encountered this as openSUSE 11.1 was rolled out, are expressing an opinion about a surprising change to the status quo.
I don’t see a problem in arguing about preferences. If it’s so irrelevant then why they bothered to change it and why the other group (of users) should get their way?
I think that both sides have strong arguments so compromise would be to add an option to /etc/sysconfig/sw_management which would
toggle this behavior.
I also miss this feature. You could indeed just open yast as a workaround, but I find it annoying that you have then 2 windows open when installing software. And I prefer as less windows opened as possible. Thats why I moved from 11.0 to 11.1: nautilus has tabs now:)
>
> Caracalla;1912552 Wrote:
>> I agree that this was not a good design decision (and i’d very much like
>> to know how they figure that a majority supports it) An ‘issue’
>> (https://bugzilla.novell.com/show_bug.cgi?id=421660) has been filed on
>> it but it seems unlikely that changes will be made. Still, it can’t hurt
>> to comment/vote.
>
> According to that “bug” report, the dev’s were responding to previously
> filed “bugs” complaining about it. I’m sympathetic to the dev’s plight;
> they are dmd if they do, dmd if they don’t. Now that package mgmt
> is so fast and the caches are refreshed only if the repo changes, it’s
> all of a single-click and few seconds to restart the program. IMHO,
> this is really trivial and there are much, much more important issues to
> argue about.
I’m screwing around with 4 boxes and either your observation about caches is
in error or they are refreshing all the repos massively - some of these
machines are a bit dated and the refresh is painfully slow. I’ve got a few
things that require a removal followed by the install of the replacement
due to dependencies in a “you can’t get there from here” arrangement and
the “new and improved” action is a royal PITA.
One comment on the bug reports: you only see reports from those who desire a
change - the ones who like it as is have nothing to complain about. Of
course, the cure is worse than the cause; imagine voting on every change???
I would submit that the real answer is even simpler: two buttons. “Accept
and exit” and “Accept and continue”. Life is about choice?
