Comments on: YaST Survey Started

By: Adam

Adam — Tue, 11 Nov 2008 06:26:03 +0000

I agree completely, on the APT base and replacing yast with debconf.

By: chrys

chrys — Sun, 27 Jul 2008 01:23:31 +0000

introduce the idea of Metalink in Yast for download;
Do you download the first with all packages and then to install them, similar to apt-get or aptitude.

By: geo

geo — Fri, 11 Apr 2008 21:11:02 +0000

Amen to that!

By: Beineri

Beineri — Thu, 28 Feb 2008 19:51:03 +0000

Look at the date of the story and http://news.opensuse.org/2007/11/17/yast-survey-finished/

By: Eduardo Bacchi Kienetz

Eduardo Bacchi Kienetz — Thu, 28 Feb 2008 19:26:38 +0000

This survey is currently closed. Please contact the author of this survey for further assistance.

???

By: Jop

Jop — Mon, 28 Jan 2008 13:13:48 +0000

Going to software repositories to enable or disable refresh is not the most comfortable way to do it. Although it’s the only one now.
I agree with many things said. Here are my 2 cents:

- Don’t update repositories when running the PM by default. Place a button in it so they can be updated at will.
That way there’s no need to code a time check to update repositories as it would rely on user.
Make that button two, so with the second you can choose which repos to update.
Yeah, I know, that’s like Smart does it and you must be tired of hearing about Smart but it has its features. ;)

- Make those darn popups one and update its content instead of calling the modal popup window for every repo so it doesn’t steal focus. If it could also stay still in one desktop and not follow you around your cube (or whatever ;)) it’d be awesome.

The idea would be to use Software repositories as few times as possible, leaving it to set up repositories and mirrors.
I think the rest is fine for me. :)
Sorry I’m a lil late, I missed it. Hope someone reads it though.

By: Benjamin Weber

Benjamin Weber — Mon, 17 Dec 2007 19:24:17 +0000

You can disable the repository refresh for a particular repository using either yast -> software repositories, or “zypper mr –disable-autorefresh ” when the repositories are up to date it takes zypper/yast approximately 1s per repository on average on my machine. Of course if you disable autorefresh you have the risk that the filename the package manager is looking for on the mirrors has since changed and it won’t be able to find it, but you can refresh manually in that case. One of the biggest culprits for slowing down the refresh process is the packman repository which changes almost every hour, meaning a new 5mb download of metadata every hour.

By: Anonymous

Anonymous — Sun, 16 Dec 2007 07:54:34 +0000

> I am forced to use the ncurses based YaST mostly because of all the repositories I subscribe too (almost all of the buildservice ones).

I don’t get why someone has to subscribe to “almost all buildservice repositories” and why this does require text-based software management.

By: PhillyMuscle

PhillyMuscle — Sun, 16 Dec 2007 02:13:11 +0000

I am forced to use the ncurses based YaST mostly because of all the repositories I subscribe too (almost all of the buildservice ones).

I write code and work in Monodevelop (I know, evil right?), and I’m a heavy VM user since I’m in a Windows shop at work that allows me to use Linux to develop Win software [but I work on Java/SAP stuff].

So, when I need to grab a simple package really fast and install it to do something, say… Scribus… it takes me almost 20 minutes because it has to refresh every stinkin repository.

Oh and worse, if you do a base OpenSUSE install, say 10.3, and then you need to update the system before you start installing your stuff because you want all the all the latest pataches… there is nothing equivalent to “make -j” so you can take full advantage of your quad-cpu-dual-core multithreaded high-bandwidth goodness.

Nope, you gotta download everything one package, slowly, at a time. Grr.

I hope OpenSUSE 11 addresses this.

And more… like all the pain of trying to use java on x86_64 vs i386.

By: GregJ

GregJ — Mon, 26 Nov 2007 04:19:09 +0000

Seems that the main issue with “YaST” is actually with “yast sw_single” and it’s reading of cached package info.

Seems since RAM is dirt cheap these days and my /var/lib/zypp directory is only 93M, the simplest solution is to daemonize zypper and replace it with a command passing script.

With a “quit” command to unlock the RPM database this might take a few hours to implement.

This plus a nightly cron job to run “zypper ref” and an /etc/zypp/zypp.conf with repo.refresh.delay = 1440 # 60 * 24 min

Of course, this ignores zypper’s key handling, and a way to force a refresh…