Bug 529197

Summary:	YaST should indicate that installing .src.rpm files won't actually install the package
Product:	[openSUSE] openSUSE 11.1	Reporter:	Forgotten User EGKOvZW2-J <forgotten_EGKOvZW2-J>
Component:	YaST2	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	dmacvicar
Version:	Final
Target Milestone:	---
Hardware:	PC
OS:	openSUSE 11.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User EGKOvZW2-J 2009-08-07 13:24:14 UTC

User-Agent:       Opera/9.64 (X11; Linux x86_64; U; en) Presto/2.1.1

Consider a simple usage scenario:
A user downloads some .src.rpm file (instead of, say, .i586.rpm, by accident). Then he/she clicks the file in Dolphin (or whatever). YaST pops up and installs the file happily. The user thinks that the program is installed, but it's nowhere to be seen. (It's actually scattered around /usr/src/packages, but there was no indication of this).

What I think YaST should do is say something like "This is a source package, you probably need a binary package instead.". Some details about possible naming of the binary packages would also be nice.

As a bonus, this would actually educate the users about difference between the .src.rpm and .(i586|x86_64|ppc|...).rpm files (I don't recall seeing this information, not even at openSUSE package search site).

Reproducible: Always




openSUSE 11.1 x86_64, KDE 4.3.0 from OBS.

Comment 1 Duncan Mac-Vicar 2009-08-07 13:43:32 UTC

No, then people looking to install src.rpm would open a bug complaining why they get a warning.

Anyways in 11.2 we delegate installing of rpms in the UI to PackageKit.

Comment 2 Forgotten User EGKOvZW2-J 2009-08-07 13:57:24 UTC

Well, that warning could have a "Don't show this warning again" checkbox, which easily fixes that.
Plus, I would say the ratio of binary installs vs source installs is so high that it would definitely be a pro than a con.

I don't know how PackageKit handles that, but if it still treats them the same, it's still a usability bug.