Dependencies (for builds and runtime) definition

[Benjamin Podszun-2]

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

[Sandy Armstrong]

Unless anybody gives reasons against it, I am 100% for this change.

GMime is kind of irritating, because it is an incompatible API and
will require more work to adapt, *plus* they are changing API again
for 2.6, but that won't be out for awhile so it's not a big concern.
A patch to the latest GMime will be non-trivial, but hopefully still
easy!

As for the rest, I am totally happy bumping Mono to 2.0, Mono.Addins
to 0.4, and gtk-sharp to 2.12.  Ben, feel free to forge ahead on this.

Thanks everybody,
Sandy

On Thu, Apr 30, 2009 at 5:38 AM, Benjamin Podszun
<benjamin.podszun@...> wrote:

> 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
>

_______________________________________________
Tomboy-list mailing list
Tomboy-list@...
http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com

[Sandy Armstrong]

Whoops, this message has been sitting in my drafts for awhile now!

On Thu, Apr 30, 2009 at 9:14 AM, Sandy Armstrong
<sanfordarmstrong@...> wrote:
> Unless anybody gives reasons against it, I am 100% for this change.
>
> GMime is kind of irritating, because it is an incompatible API and
> will require more work to adapt, *plus* they are changing API again
> for 2.6, but that won't be out for awhile so it's not a big concern.
> A patch to the latest GMime will be non-trivial, but hopefully still
> easy!

Jeff Stedfast fixed this; we now support GMime 2.2.x and 2.4.x in Tomboy 0.15.0.

> As for the rest, I am totally happy bumping Mono to 2.0, Mono.Addins
> to 0.4, and gtk-sharp to 2.12.  Ben, feel free to forge ahead on this.

We will definitely have the following new version dependencies:

mono 1.9.1
gtk+ 2.12 (2.14 conditionally supported for some new API)
gtk-sharp 2.12

I'd like to require Mono.Addins 0.4 just because it is more stable,
but fairly recent distros like openSUSE 11.0 and Ubuntu 8.10 only have
0.3.  Since this is more about stability than new API, I am
comfortable requiring Mono.Addins 0.3, but recommending Mono.Addins
0.4.  For Windows, however, we have moved to Mono.Addins 0.4 since
Tomboy 0.15.0.

Thanks for everybody's input,
Sandy
_______________________________________________
Tomboy-list mailing list
Tomboy-list@...
http://lists.beatniksoftware.com/listinfo.cgi/tomboy-list-beatniksoftware.com