Bug 22976 - Mono.Cairo duplicates cairo-sharp in the gtk-sharp repository
Summary: Mono.Cairo duplicates cairo-sharp in the gtk-sharp repository
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: Mono.Cairo ()
Version: master
Hardware: PC All
: --- normal
Target Milestone: Untriaged
Assignee: Jo Shields
Depends on:
Reported: 2014-09-14 06:09 UTC by Antonius Riha
Modified: 2015-12-24 15:02 UTC (History)
3 users (show)

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 22976 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:

Description Antonius Riha 2014-09-14 06:09:16 UTC
Mono.Cairo code in the mono repository is more or less the same as the cairo-sharp code in the gtk-sharp repository. This has several disadvantages:
 * For library consumers:
     - It raises the question, which library to use, if there are differences and if yes, which.
     - Documentation about the library may apply to one version but not to the other (at least you get confused).
 * For library devs:
     - Duplicate effort to keep the bindings up-to-date
     - Keeping the APIs in sync (if that's even desired)
     - Applying bug fixes in 2 places
     - Updating documentation in 2 places
     - ...

My opinion is that cairo-sharp and Mono.Cairo do the same thing and thus should be the same thing.
Comment 1 Miguel de Icaza [MSFT] 2015-12-24 15:02:20 UTC
Mono.Cairo originated in Mono, it looks like someone extracted it and placed it on gtk-sharp.

Perhaps we need to extract Mono.Cairo as its individual top level, and we need to merge whatever improvements were done to one, but not the other into the extracted version.