Update eclasses and profiles. Since python2.6 has been dropped from the
allowed list in the python eclass all ebuilds must stop referring to it
so a extra ebuilds have to get pulled in with this change.
Packages removed:
dev-python/argparse
virtual/python-argparse
virtual/python-unittest2
Packages updated:
app-portage/gentoolkit
dev-lang/python-exec
dev-libs/boost
dev-libs/libxml2
dev-libs/libxslt
dev-python/dbus-python
dev-python/logilab-common
dev-python/lxml
dev-python/mock
dev-python/pygobject
dev-util/cmake
dev-vcs/git
eclass
licenses
profiles
scripts
sys-devel/automake
sys-devel/automake-wrapper
sys-fs/cryptsetup
Update glib and assorted dependencies, our version is so out of date it
prevents updating other ebuilds.
Packages updated:
app-text/yelp-tools
dev-libs/dbus-glib
dev-libs/expat
dev-libs/glib
dev-libs/gobject-introspection
dev-libs/gobject-introspection-common
dev-libs/libffi
dev-util/gdbus-codegen
dev-util/gtk-doc
dev-util/gtk-doc-am
dev-util/itstool
gnome-extra/yelp-xsl
virtual/libffi
virtual/libiconv
The path for network leases has been change in recent versions
of systemd. This fix modified the DHCP server resolution script
used by CloudStack to reflect this change.
Most of the change here isn't significant except for the compilation
fixes for compiling with a hardened compiler. This was not an issue
previously because the SDK's cross compiler wasn't hardened.
The default 10.0 is deprecated and removed upstream. Also, instead of
twiddling the hardened flag we should just use the hardened profile.
As part of this the host SDK no longer has multilib enabled, it isn't
actually needed for anything anyway.
When enabling policy kit there appears to be a build race condition in
the generation of updating translations in policy files. There is a nls
configure flag in systemd now, we don't need translations.
The existing ebuild uses a really crazy hack for cross compiling which
may have worked a few versions ago but it doesn't now. The root issue is
that Mozilla mixes up the meaning of "host" and "target" so give in to
their stupid and setup the environment with their meaning.
The configure script claimed in a comment:
In Mozilla, we use the names $target, $host and $build incorrectly,
but are too far gone to back out now. See Bug 475488:
- When we say $target, we mean $host, that is, the system on which
Mozilla will be run.
- When we say $host, we mean $build, that is, the system on which
Mozilla is built.
- $target (in its correct usage) is for compilers who generate
code for a different platform than $host, so it would not be used
by Mozilla.
I'm inclined to smack someone with a stick.
