[gentoo-dev] Changes in installed ebuilds

[Jörg Schaible]

Hi,

can somebody tell my, since when existing (and installed) ebuilds suddenly 
change without at least increasing the version number?

Today's synchronization got me suddenly dependency conflicts for installed 
packages:

==================== %< =========================
!!! All ebuilds that could satisfy ">=dev-libs/glib-2.38.2-
r1:2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?]" 
have been masked.
!!! One of the following masked packages is required to complete your 
request:
- dev-libs/glib-2.40.0-r1::gentoo (masked by: ~amd64 keyword)
- dev-libs/glib-2.38.2-r1::gentoo (masked by: package.mask)

(dependency required by "dev-libs/dbus-glib-0.100.2-r1" [installed])
(dependency required by "sys-auth/consolekit-0.4.6" [installed])
(dependency required by "sys-auth/polkit-0.112-r1[-systemd]" [installed])
(dependency required by "sys-fs/udisks-2.1.2" [installed])
(dependency required by "kde-base/kdelibs-4.12.5-r1[udisks]" [ebuild])
(dependency required by "kde-base/nepomuk-widgets-4.12.5" [installed])
==================== %< =========================

Diffing the ebuilds for dbus-glib:

==================== %< =========================
~ $ locate dbus-glib-0.100.2-r1.ebuild
/var/db/pkg/dev-libs/dbus-glib-0.100.2-r1/dbus-glib-0.100.2-r1.ebuild
/var/db/portage/central/dev-libs/dbus-glib/dbus-glib-0.100.2-r1.ebuild
~ $ diff -u `locate dbus-glib-0.100.2-r1.ebuild`
--- /var/db/pkg/dev-libs/dbus-glib-0.100.2-r1/dbus-glib-0.100.2-r1.ebuild       
2014-02-24 09:01:29.779074662 +0100
+++ /var/db/portage/central/dev-libs/dbus-glib/dbus-glib-0.100.2-r1.ebuild      
2014-06-18 21:31:11.000000000 +0200
@@ -1,6 +1,6 @@
 # Copyright 1999-2014 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/dev-libs/dbus-glib/dbus-glib-0.100.2-
r1.ebuild,v 1.7 2014/02/23 16:17:58 pacho Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-libs/dbus-glib/dbus-glib-0.100.2-
r1.ebuild,v 1.11 2014/06/18 19:09:23 mgorny Exp $
 
 EAPI=5
 inherit bash-completion-r1 eutils multilib-minimal
@@ -11,18 +11,18 @@
 
 LICENSE="|| ( GPL-2 AFL-2.1 )"
 SLOT="0"
-KEYWORDS="~alpha amd64 arm hppa ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc x86 
~amd64-fbsd ~x86-fbsd ~x86-interix ~amd64-linux ~arm-linux ~x86-linux ~ppc-
macos ~x86-macos ~m68k-mint ~sparc-solaris ~x86-solaris"
+KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ppc64 ~s390 ~sh sparc x86 
~amd64-fbsd ~x86-fbsd ~x86-interix ~amd64-linux ~arm-linux ~x86-linux ~ppc-
macos ~x86-macos ~m68k-mint ~sparc-solaris ~x86-solaris"
 IUSE="debug doc static-libs test"
 
-CDEPEND=">=dev-libs/expat-2[${MULTILIB_USEDEP}]
-       >=dev-libs/glib-2.26:2[${MULTILIB_USEDEP}]
-       >=sys-apps/dbus-1.6.2[${MULTILIB_USEDEP}]"
+CDEPEND=">=dev-libs/expat-2.1.0-r3[${MULTILIB_USEDEP}]
+       >=dev-libs/glib-2.38.2-r1:2[${MULTILIB_USEDEP}]
+       >=sys-apps/dbus-1.6.18-r1[${MULTILIB_USEDEP}]"
 DEPEND="${CDEPEND}
        virtual/pkgconfig
        doc? ( >=dev-util/gtk-doc-1.4 )"
 RDEPEND="${CDEPEND}
-        abi_x86_32? (
-               !<app-emulation/emul-linux-x86-baselibs-20131008-r8
+       abi_x86_32? (
+               !<app-emulation/emul-linux-x86-baselibs-20131008-r8
                !app-emulation/emul-linux-x86-baselibs[-abi_x86_32(-)]
        )"
 
@@ -49,7 +49,7 @@
                $(use_enable debug verbose-mode)
                $(use_enable debug asserts)
                $(use_enable static-libs static)
-               $(multilib_build_binaries && use_enable doc gtk-doc || echo 
" --disable-gtk-doc")
+               $(multilib_native_use_enable doc gtk-doc)
        )
 
        ECONF_SOURCE="${S}" econf "${myconf[@]}"
==================== %< =========================

So, why the heck, was the dependency to dev-libs/glib changed for an 
existing ebuild without increasing its version (e.g. dbus-glib-0.100.2-r2)? 
Who can really say, that dbus-glib still works properly without having been 
compiled against those new versions of expat, glib and dbus? Sorry, but this 
is simply bad practice.

I have to use an older Eclipse 3.8.x version for my daily work and since it 
is broken with latest gtk versions (a lot of crashes), I use still some old 
ebuilds and have masked new ones. However, if the dependencies of installed 
ebuilds suddenly change, this simply breaks my portage tree.

- Jörg