![]() ![]() We currently ship a few packages, and we should make the re-packaging a standard part of our process, subscribing to the various groups that we need to: Plans on how to split the MacOS installer into Runtime and SDK Ongoing Maintenance of third party components We need to sort out the distribution for Windows.ĭistribution of Gtk+ and Gtk# for MacOS X. In addition to the Gtk#-based applications that we have (and I believe we package most of this), I can think of the following classes of applications that we should package: Windows and MacOS packaging Starting with one or two platforms for now is fine, we do not need to build on every platform, I rather have us jump-start the effort and get a lot of software only on openSUSE and later add more platforms (SLED, RHEL, etc). (We may want to establish a packaging naming standard, similar to how the perl/python/etc as well as debian cil packages are named). We should use the openSUSE build system, as this would allow us to support multiple platforms in the future as well. We should package libraries, components and applications so we can more easily QA the Mono runtime, verify that there are no regressions, reduce the duplicated effort in the team to test software, provide software in an easy way for people to demo and try out and to function as a reference of how applications are ported from Windows to Linux using Mono. Silverlight APIs (not ready to do yet).Olive class libraries (they are generated, but are still inside Novell’s firewall.We currently track the status of Mono vs various APIs in the class status page, we should augment this to cover: 3.3 Windows Host that runs our test suite against MS. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |