Bug 23479 - Gapi should not be contained in the gtk-sharp repository
Summary: Gapi should not be contained in the gtk-sharp repository
Status: NEW
Alias: None
Product: Gtk#
Classification: Mono
Component: gtk-sharp ()
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-09-30 02:12 UTC by Antonius Riha
Modified: 2014-10-03 17:23 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 23479 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 Antonius Riha 2014-09-30 02:12:41 UTC
The GAPI tools
 * gapi3-parser
 * gapi3-fixup
 * gapi3-codegen
don't have any dependency on gtk-sharp and should work for all bindable native libraries. Hence they should have their own repository and package. In fact some distributions already have GAPI-specific packages like "gtk-sharp3-gapi" in Debian-based ditros.
Aside from the conceptual justification for the split, GAPI would get more exposure, if it had its own repo. This is because bindings authors of any native library - gtk-sharp devs excluded - usually wouldn't anticipate GAPI being part of gtk-sharp and thus have difficulties in contributing improvements to GAPI.
Development and release management would also profit from a split: GAPI versions would not have to be tied to gtk-sharp versions any more and GAPI can thus have its own release cycle. GAPI developers can concentrate on GAPI development and don't have to account for the gtk-sharp build not to break.
Comment 1 Antonius Riha 2014-10-03 17:23:04 UTC
I've created a gapi-sharp repsoitory here: https://github.com/antoniusriha/gapi-sharp and a pull request with the respective changes to gtk-sharp here: https://github.com/mono/gtk-sharp/pull/124