nixpkgs/pkgs/desktops/gnome-2.28/platform/gnome-vfs/default.nix

{ stdenv, fetchurl, pkgconfig, libxml2, bzip2, openssl, samba, dbus_glib, glib, fam, hal, cdparanoia
, intltool, GConf, gnome_mime_data}:

stdenv.mkDerivation {
  name = "gnome-vfs-2.24.1";
  
  src = fetchurl {
    url = mirror://gnome/sources/gnome-vfs/2.24/gnome-vfs-2.24.1.tar.bz2;
    sha256 = "1dmyr8nj77717r8dhwkixpar2yp8ld3r683gp222n59v61718ndw";
  };
  
  buildInputs =
    [ pkgconfig libxml2 bzip2 openssl samba dbus_glib fam hal cdparanoia
      intltool gnome_mime_data
    ];

  propagatedBuildInputs = [ GConf glib ];
}
Adding Gnome-2.28 sources svn path=/nixpkgs/trunk/; revision=17519 2009-09-30 07:27:34 +02:00			`{ stdenv, fetchurl, pkgconfig, libxml2, bzip2, openssl, samba, dbus_glib, glib, fam, hal, cdparanoia`
			`, intltool, GConf, gnome_mime_data}:`

			`stdenv.mkDerivation {`
			`name = "gnome-vfs-2.24.1";`
* 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-04 00:26:14 +01:00
Adding Gnome-2.28 sources svn path=/nixpkgs/trunk/; revision=17519 2009-09-30 07:27:34 +02:00			`src = fetchurl {`
Oops. A typo in a fix for a fix of a typo.. svn path=/nixpkgs/trunk/; revision=17529 2009-09-30 08:35:09 +02:00			`url = mirror://gnome/sources/gnome-vfs/2.24/gnome-vfs-2.24.1.tar.bz2;`
Oops, typos in automated update svn path=/nixpkgs/trunk/; revision=17523 2009-09-30 08:10:45 +02:00			`sha256 = "1dmyr8nj77717r8dhwkixpar2yp8ld3r683gp222n59v61718ndw";`
Adding Gnome-2.28 sources svn path=/nixpkgs/trunk/; revision=17519 2009-09-30 07:27:34 +02:00			`};`
* 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-04 00:26:14 +01:00
			`buildInputs =`
			`[ pkgconfig libxml2 bzip2 openssl samba dbus_glib fam hal cdparanoia`
			`intltool gnome_mime_data`
			`];`

			`propagatedBuildInputs = [ GConf glib ];`
Adding Gnome-2.28 sources svn path=/nixpkgs/trunk/; revision=17519 2009-09-30 07:27:34 +02:00			`}`