Bug 277973

Summary:	packaging: please allways put app names in the summary if the package is multi-app one
Product:	[openSUSE] openSUSE 10.2	Reporter:	macias - <bluedzins>
Component:	YaST2	Assignee:	Dirk Mueller <dmueller>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i586
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description macias - 2007-05-24 18:48:10 UTC

In such cases I have to:
a) search in package description
b) I have to know in advance where to search

It is not very productive from the user point of view.

For example, if I would search for quanta (0 results) it would be nice if it actually show
kdewebdev KDE web developer suite (Quanta, sth else, etc.)
so I could actually get one hit.

Comment 1 Ladislav Slezák 2007-05-29 13:02:39 UTC

Reassigned to kdewebdev3 maintainer...

Comment 2 Dirk Mueller 2007-05-29 13:30:36 UTC

which package installer do you use for searching?

Comment 3 macias - 2007-05-29 16:39:00 UTC

Ladislav, kdewebdev was just an example.

Dirk, I am using yast.

Comment 4 Dirk Mueller 2007-05-30 15:19:12 UTC

kdewebdev3 contains Quanta in the description.

Comment 5 macias - 2007-05-30 15:30:08 UTC

Yes, I know, but my wish concerns summary, not description. If you have slow (?) computer and a lot (10-15) of repos searching in summaries vs. descriptions can be a difference. Currently you have to make two searches because you can never be sure if you don't have package in repo or it is in multipack and you have to search again in description for it.

Comment 6 Ladislav Slezák 2007-06-04 07:45:18 UTC

To comment #3: OK, if there are more affected packages then you have to fill a separate bug report for each package (sorry, it's not convenient, but there is no other way).

Yast doesn't (and cannot) know which applications are inside a package. It's a task for the respective package maintainer to describe the package well.

Reassigning back to the kdewebdev maintainer, yast cannot solve this problem...

Comment 7 Stephan Binner 2007-06-04 14:21:57 UTC

Small note: with the KDE 4 packages we have one package per application where the package name contains the application name. So this "problem" will vanish.

Comment 8 Dirk Mueller 2007-06-05 10:54:15 UTC

ok, I've added it for kdewebdev3, as I can see that this is a valid issue here (the module name has nothing to do with the applications in it).