Bug 22064 - Mono Class Outline Viewer command "monop" clashes with other app
Summary: Mono Class Outline Viewer command "monop" clashes with other app
Status: NEW
Alias: None
Product: Tools
Classification: Mono
Component: other ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-08-13 11:18 UTC by Jo Shields
Modified: 2014-08-13 11:18 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 22064 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description Jo Shields 2014-08-13 11:18:03 UTC
The "monop" command runs the Mono Class Outline Viewer

However, "monop" has been a part of the BSD "games" package since 1993, offering a crude Monopoly implementation.

This causes problems for users looking to install both Mono and BSD games on the same system - e.g. Debian has the "bsdgames" package which runs into this conflict. The usual solution is per-distribution renaming of commands, which is far from ideal as it means instructions on tool use differ per-distribution.