Looks like some ancient development environment script.
I actually use something very similar for my own development
environment, but it doesn't belong in a version control system.
Not the next stable version. If migration needs to occur multiple times
during a development cycle for different reasons, we'll need an accurate
last-used-version stamp.
With the removal of the 'experimental' plugin group, passing
--enable-plugins=experimental to configure will now cause the Makefile
to try and build a plugin named 'experimental', which will result in a
mysterious "experimental: No such file or directory" build error.
This is because of the "list" fallback behavior: if the option is not
one of "no", "base" or "all" then the configure script assumes it to be
a list of plugin names. I've never known that to be useful to anyone,
so remove the "list of plugin names" behavior and replace it with an
informative error message.
Eventually the --enable-plugins will be removed entirely since EPlugin
is deprecated.
GNOME has included libnotify 0.7.x since GNOME 3.0. It's still an
optional dependency for Evolution, but if you're gonna use it you'll
need a GNOME3-era release.
audio-inline, itip-formatter, prefer-plain, tnef-attachments
and vcard-inline plugins were converted to modules so that they
can fit into concept of the new formatter.
Every module still installs .eplug file, because there is no
suitable API at the moment to register plugins to the plugins dialog
and to extend the Preferences dialog.
We're using version 1.1 of Mozilla's ClientConfig format now. These
files are all version 1.0. But even aside from that, offline autoconfig
is not compelling enough to warrant maintaining two copies of this data.
This breaks a good chunk of logic out of EMAccountEditor and hopefully
makes it less brittle. Because honestly, every time I fix one thing in
EMAccountEditor it breaks three other things. It's unmaintainable.
The evolution-settings capplet was originally designed for Anjal, it was
used in MeeGo as part of the Express Mode effort, but doesn't really fit
in GNOME 3 nowadays (nor did it really fit in GNOME 2, in my opinion).
Add a --with-capplet configure switch defaulting to 'no'. The capplet
will eventually be removed unless I see someone actively maintaining it.
gweather-3.5 introduces API changes we do not yet support.
A patch for gweather-3.5 support exists in bug 672805, but since our
policy forbids requiring unstable libraries, gweather-3.4 support must
be retained until GNOME 3.6 is released. gweather-3.5/3.6 support will
remain optional until 3.7.1.
Suppress deprecated declaration warnings, particularly from GTK+, until
we're ready to care again. Once we require GTK+ 3.4 we can start using
the new deprecation min/max macros.
