Monodevelop missing from Ubuntu Software Center's "Mono/CLI" subsection

Bug #546936 reported by Matthew Paul Thomas
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
monodevelop (Ubuntu)
New
Undecided
Unassigned
software-center (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: monodevelop

1. In Ubuntu Software Center, navigate to "Get Software" > "Developer Tools" > "Mono/CLI".
2. Try to find Monodevelop.

What happens: You can't.
What should happen: You can.

This is because the monodevelop package has "Section: universe/devel". It should have "Section: universe/cli-mono".

Ubuntu Software Center could work around this temporarily by special-casing monodevelop in its categorization scheme.

Tags: metadata
tags: added: metadata
Revision history for this message
Jo Shields (directhex) wrote :

There are a couple problems with changing the section:

* MonoDevelop can be used to develop non-Mono/CLI apps, e.g. C, C++, Python, Vala, Java
* cli-mono isn't really for apps anyway - I wouldn't put Pinta or GNOME Do there either

Really, the software center should be using debtags to handle grouping, since it's pretty rare for compartmentalization like this to be correct for all cases - an app with multiple shoes to fill should appear in every possible section which fits the bill, not a single section.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

I agree that debtags would be a more flexible way of handling categorization, though we can't do that until bug 57418 is fixed. And this isn't the first time we've tripped over the problem of the Debian Section values not having official definitions. But in the meantime, Ubuntu Software Center has been treating the language-/runtime-related Section values as if they meant "items useful when developing software using this language/runtime". This works very well, with a few isolated exceptions (e.g. bug 546968).

Some of these items in these subsections are applications, but most are not; they're libraries, bindings, and so on. Neither Pinta nor Gnome Do appear in "Developer Tools" > "Mono/CLI", because neither of them are in a "cli-mono" Section; they're in "universe/gnome" and "graphics" respectively. (And Gnome Do has a .desktop file that would trump the Section value anyway.)

It's a reasonable point that MonoDevelop can be used to develop non-Mono applications, so it should, and does, appear in the general "IDEs" subsection -- but since it is the centerpiece of Mono development, perhaps it should *also* be present inside "Mono/CLI" but not inside "Ruby" and "Java" and so on. Does that seem reasonable?

If so, we have a mechanism worked out just for this: X-Ubuntu-Category-Secondary. The way to get this going is to add "X-Ubuntu-Category-Secondary: Mono" to MonoDevelop's .desktop file. Then the USC developers can take care of the rest.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

directhex, you said "cli-mono isn't really for apps anyway". But even if that was true formerly, it doesn't seem to be now: <http://packages.debian.org/unstable/cli-mono/> includes monodevelop. So not only would this would be a one-line fix to make Monodevelop more visible to potential Mono developers, it also seems to have the advantage of being technically correct. :-) Therefore I'm marking this as Won't Fix for USC; it should be fixed in the monodevelop package.

(Since my previous comment, Pinta now *does* wrongly appear in "Developer Tools" > "Mono/CLI" because of bug 554180, but that doesn't affect this bug.)

Changed in software-center (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.