search

mono / mono

Mono open source ECMA CLI, C# and .NET implementation.
https://www.mono-project.com
Other
11.13k stars 3.82k forks source link

Split Mono.Cairo out #12569

Open decriptor opened 5 years ago

decriptor commented 5 years ago

Currently Mono.Cairo is included in the mono repository. Is it worth splitting it out into it's own repository and creating a nuget package from it.

I was recently working on a project on Windows that uses Mono.Cairo. I was getting compile errors because of a missing method. After investigating a bit I noticed that the version of Mono.Cairo that is included with the gtk-sharp msi installer for Windows included an older version of Mono.Cairo. This got me thinking that it'd be nice to have it split out and publish the assembly on nuget so that we could easily have a consistent version across all platforms and not have it tied to the mono repository.

Thoughts?

decriptor commented 5 years ago

/cc @akoeplinger @Therzok @bratsche @directhex thoughts?

Maybe also things like Mono.Posix specifically things like Catalog?

akoeplinger commented 5 years ago

@marek-safar what are your thoughts on splitting out Mono.Cairo (and other Mono.* stuff) ?

marek-safar commented 5 years ago

We usually do it only for code where we see a potential for future improvements and development. If the nuget packaging is the only "addition" to what we have today I'd much prefer to allow building the package from Mono than moving code around

migueldeicaza commented 5 years ago

Exactly, we can keep the code here, and just add the NuPkg files to do the build.

Additionally, we can setup easily an Azure Pipelines job that publishes new versions of the library.

But perhaps Mono.Cairo could get more action if it was split up, but it brings the burden on Mono to bring another submodule.