Mono Backports

Brandon Hale brandon at smarterits.com
Wed Jul 27 16:22:50 CDT 2005


mono-mcs is no longer its own source package.
After we build mono (the source package) we will have mono-mcs.
An example of why you don't start at the top of the stack and hope
things just work themselves out.

Thanks,
Brandon Hale

On Wed, 2005-07-27 at 19:50 +0100, Martin Meredith wrote:
> gtk-sharp2-unstable was queued....
> 
> and on a dep-wait for mono-mcs..
> 
> Some of the mono stuff may need to be changed in breezy to have the like
> Dependencies on the right version of mono stuff.
> 
> :D
> 
> 
> 
> Brandon Hale wrote:
> > Hi,
> > 
> > I would like to coordinate with the Backports team to create a solid set
> > of Mono backports for Hoary.
> > 
> > There are major changes between Mono packaging in Hoary to Breezy.
> > We updated to a new major version of the core, and most file locations are
> > moved back to upstream defaults (/usr/share/dotnet to /usr/lib/mono).
> > 
> > For this reason, it is not feasible to backport individual Mono packages
> > to Hoary.  Lets do this right and work our way up the dependency chain to
> > build a clean framework for Hoary.  Once we have this base we can go
> > forward only pulling one package at a time.
> > 
> > cli-common contains debhelper scripts used by all packages.  This is
> > already backported.  Next we can do Mono core (source package mono),
> > followed by gtk-sharp, gtk-sharp2-unstable, and then the other bindings,
> > and finally apps.
> > Lets kick things off with mono and gtk-sharp and see how things go.
> > 
> > Thanks,
> > Brandon Hale
> > 
> > 
> 




More information about the Ubuntu-backports mailing list