Bug 231159

Summary:	Four suggested enhancements to the YaST system
Product:	[openSUSE] openSUSE 10.3	Reporter:	Hadron S <scx.dps>
Component:	YaST2	Assignee:	Jiri Srain <jsrain>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	scx.dps
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	SUSE Other
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Hadron S 2006-12-30 11:12:36 UTC

Hello, here I post my ideas in order of priority.

1) Automated mirroring.
The repodata files has a unique md5sum, as this md5sum will be the same on 
every mirror, YaST could detect whenever there are more than one servers with 
the same packages, so that YaST would be able to auto-detect and configure 
those sources as mirrors, instead of adding these as new sources.

 --------------------------------------------------------------------- 

2) When editing installation sources, the sources are being refreshen every 
time something is modified, we could make the refresh of the sources to take 
place only after clicking "finish" or explicitly by the user, otherwise it is 
a bit annoying and time consuming.

3) To pause and resume an update or an installation process. 
It would be useful specially for PC's without access to a broadband 
connection, for instance when I had dial up, I had to keep the PC running for 
long hours just to get updates. There are times when people just can't get 
access to broadband connections or simply can't afford it, in the country I 
was living, DSL is too expensive so that everyone uses dial-up. 

4) Something to customize YaST ncurses appearance. 
I can thing of a very simple script able to switch ncurses colours from blue 
to green or red or b/w; it could be added to the sysconfig module maybe ? 
I don't think there would have much sense to do the same with the GUI 
interface though.

Comment 1 Matej Horvath 2006-12-31 13:57:37 UTC

Thank you for your response and support. But, please, do not write more than one enhancement/bug in one report.

Comment 3 Jiri Srain 2007-01-05 09:48:20 UTC

1) I understand this requirement, however, the fact that two sources are the same in one moment doesn't mean that they will keep the same in the future (so I'd like to avoid making any relationship between the sources based on an MD5 checksum. OTOH, it can make sense to
- check MD5sum before downloading/refreshing the metadata against other existing sources
- build the relationship (if we can make use of it) on the fly when initializing YaST/ZYPP. I will add an entry to the feature database.

2) Added to feature database.

3) Even though your reasons sound reasonable, i don't think it is a good idea to stop any package manager translation. The reason is that in such case you have an inconsistent system (eg. foo-1 and foo-devel-2) due to partly updated system. I suggest you should update/install only the minimal requireded set of packages in such situations.

4) Added an entry to feature database

Resolving bug as LATER (items 1,2,4 were added to feature database and will be evaluated according to the feature process)

Comment 5 Hadron S 2007-01-07 01:56:40 UTC

1) Ok, that "dynamic mirroring" you sounds much smarter, I really, really like the idea. :D

3) Well that's another thing, YaST uses to: 
"download package1" "install package1"
"download package2" "install package2"
and so on, 

But it is also time consuming, what I propose is YaST to download the packages, once all are downloaded, then will be installed, just alike to "smart" packagemanager in this case. Smart automatically resumes the instalation of packages. If an instalation or update is paused, whenever the user tries again that package, if it is already downloaded, there's no need to download it again, and simply continues downloading the remaining packages.

Even if pause/resume is were not reliable, the part about YaST downloading all files and after that installing would be not only faster but safer also if we consider the eventuality of a server going down in the middle of the instalation.

Id est:
"download package1" "download package2" "download package3"
"install package1" "install package2" "install package3"

Thank you. (really)

Comment 6 Jiri Srain 2007-01-09 12:22:25 UTC

We have already discussed the idea "download everything first, then install", however, it doesn't work if you are running out of disk space (in this case, in addition to all the files in the packages you need space for all the RPMs).

One more idea, which is being discussed as well, is to download next package while previous one is being installed.

These ideas are already discussed in SUSE, however, I don't expect them to be implemented in next release (due to complexity).

Comment 7 Katarina Machalkova 2007-06-15 11:44:09 UTC

Feature #4 is now done.
From yast2-2.15.37 and yast2-ncurses-2.15.19 on, you can switch between available ncurses color themes using Y2NCURSES_COLOR_THEME variable in /etc/sysconfig/yast2 :-)

Comment 8 Ladislav Slezák 2007-07-23 16:33:40 UTC

Feature #2 is implemented in yast2-packager-2.15.48 (and in yast2-pkg-bindings-2.15.32)

Comment 9 Bugzilla Account Maintenance 2008-09-02 18:07:47 UTC

Because the LATER and REMIND resolutions have been removed, the resolution of this bug has changed from LATER to WONTFIX. If this bug needs to be reconsidered, reopen it and set a future "Target Milestone for Fix."