nixpkgs/pkgs/desktops/gnome-2/platform/GConf/default.nix

{ stdenv, fetchurl, pkgconfig, dbus_glib, glib, ORBit2, libxml2
, polkit, intltool, dbus_libs }:

stdenv.mkDerivation {
  name = "GConf-2.28.1";

  src = fetchurl {
    url = mirror://gnome/sources/GConf/2.28/GConf-2.28.1.tar.bz2;
    sha256 = "001h9gngz31gnvs6mjyazdibhdqmw1wwk88n934b0mv013wpgi2k";
  };

  buildInputs = [ pkgconfig ORBit2 dbus_libs dbus_glib libxml2 polkit intltool ];
  propagatedBuildInputs = [ glib ];
}
* Several buildInputs of Gnome-related packages should be propagatedBuildInputs, because those inputs are required by the .pc or .la files of the package: - If a .pc file references a non-propagated input, then Gnome packages have the bad tendency to silently ignore this problem in configure scripts - the failure of a command like `pkg-config --cflags foo' will be ignored if a dependency of foo.pc is missing, so no flags will be added, and the build will fail later on a missing header or library. - If a .la file references a non-propagated input, the build will also fail, because Libtool will add library dependencies that it cannot find. (Arguably .la files should never reference packages that aren't in the corresponding .pc file, but they do it anyway). By setting the propagatedBuildInputs properly, it should be possible to get rid of all the NIX_CFLAGS_COMPILE / NIX_LDFLAGS hacks in the Gnome expressions. svn path=/nixpkgs/branches/xorg-7.5/; revision=18084 2009-11-03 15:26:14 -08:00			`{ stdenv, fetchurl, pkgconfig, dbus_glib, glib, ORBit2, libxml2`
GConf-2.28.1, policykit->polkit svn path=/nixpkgs/trunk/; revision=31333 2012-01-05 16:55:14 -08:00			`, polkit, intltool, dbus_libs }:`
Adding Gnome-2.28 sources svn path=/nixpkgs/trunk/; revision=17519 2009-09-29 22:27:34 -07:00
			`stdenv.mkDerivation {`
GConf-2.28.1, policykit->polkit svn path=/nixpkgs/trunk/; revision=31333 2012-01-05 16:55:14 -08:00			`name = "GConf-2.28.1";`

Adding Gnome-2.28 sources svn path=/nixpkgs/trunk/; revision=17519 2009-09-29 22:27:34 -07:00			`src = fetchurl {`
GConf-2.28.1, policykit->polkit svn path=/nixpkgs/trunk/; revision=31333 2012-01-05 16:55:14 -08:00			`url = mirror://gnome/sources/GConf/2.28/GConf-2.28.1.tar.bz2;`
			`sha256 = "001h9gngz31gnvs6mjyazdibhdqmw1wwk88n934b0mv013wpgi2k";`
Adding Gnome-2.28 sources svn path=/nixpkgs/trunk/; revision=17519 2009-09-29 22:27:34 -07:00			`};`
GConf was wrong about include file location.. svn path=/nixpkgs/trunk/; revision=17532 2009-09-29 23:50:32 -07:00
GConf-2.28.1, policykit->polkit svn path=/nixpkgs/trunk/; revision=31333 2012-01-05 16:55:14 -08:00			`buildInputs = [ pkgconfig ORBit2 dbus_libs dbus_glib libxml2 polkit intltool ];`
* Several buildInputs of Gnome-related packages should be propagatedBuildInputs, because those inputs are required by the .pc or .la files of the package: - If a .pc file references a non-propagated input, then Gnome packages have the bad tendency to silently ignore this problem in configure scripts - the failure of a command like `pkg-config --cflags foo' will be ignored if a dependency of foo.pc is missing, so no flags will be added, and the build will fail later on a missing header or library. - If a .la file references a non-propagated input, the build will also fail, because Libtool will add library dependencies that it cannot find. (Arguably .la files should never reference packages that aren't in the corresponding .pc file, but they do it anyway). By setting the propagatedBuildInputs properly, it should be possible to get rid of all the NIX_CFLAGS_COMPILE / NIX_LDFLAGS hacks in the Gnome expressions. svn path=/nixpkgs/branches/xorg-7.5/; revision=18084 2009-11-03 15:26:14 -08:00			`propagatedBuildInputs = [ glib ];`
Adding Gnome-2.28 sources svn path=/nixpkgs/trunk/; revision=17519 2009-09-29 22:27:34 -07:00			`}`