Packaging Mono Applications

It's currently not supported (out of the box) to package mono applications using Autopackage. See the bug list below for details on what's left to do, and how far we've come today.

It will probably never be possible (unless Novell picks up this one) to retrieve the actual mono framework from autopackage. Mono is a system package, and should most likely not be packaged using autopackage.

How it's supposed to work (if above bugs were fixed)

It should be possible to detect both the .NET profile of the current runtime, aswell as the actual mono release version. These will be returned by the skeleton, and it will be possible for a package to say

  • I can only run on Mono version 1.2 and higher
  • I can only run on a runtime supporting the .NET 1.1 profile

An example would be 

[Prepare]
# Depend on a specific .NET profile (in this case .NET 1.1)
require @mono-project.com/mono 1.1
# or depend on a specific mono release:
requireAtLeast "@mono-project.com/mono:1.2"