Re: Dependencies (for builds and runtime) definition

> Hi.
>
> I'd like to raise the question of dependency versions again. The following
> dependencies come from the top of my head and should imo be defined for 0.15
> to allow patches for deprecation warnings and contributions that make use of
> new functionality early in this cycle.
>
> - Mono 2.0
>  Build time would give us type inference, object initializers. Runtime could
> offer LINQ as the most desireable feature
>
> - Mono.Addins 0.4
>  Improvements on Windows (no console Windows that pop up during startup),
> fixes bug 575624 and 572088 (the latter explicitly requests this version)
>
> - GTK 2.12
>  Already the version used on Windows. Actually I'm not sure what the
> improvements on the other platforms are, but we could remove a lot of
> deprecated/obsolete things from our code which generates warnings on newer
> versions
>
> - GMime 2.4
>  Requested in bug 565336
>
> Defining a target version for these dependencies (and possible other thigns
> I missed) would allow us to either work on that support _now_ or push back
> the dependent things (like the bug).
> Especially the gtk# and mono versions are interesting.
>
> Just for reference: Banshee, which recently made some frontpages because it
> was suggested to be the new/next Ubuntu default media player, requires
> according to [1]:
>
> - Mono >= 2.0
> - Mono.Addins >= 0.4
> - GTK# >= 2.12
>
> Sandy: You said that some deployments are quite large and cannot easily
> upgrade/are stuck with older versions of these libraries. Are those people
> on this list?
> Anyone else having special requirements that rule out any of these
> dependencies? Do people care about build time dependencies at all?
>
> Would love to get some feedback.
> Ben
>
> 1: http://packages.ubuntu.com/jaunty/banshee
> _______________________________________________
> Tomboy-list mailing list
> Tomboy-list@...
> http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com
>