nixpkgs/pkgs/development/libraries/xylib/default.nix

{ stdenv, fetchurl, boost, zlib, bzip2 }:

let
  name    = "xylib";
  version = "1.3";
in
stdenv.mkDerivation {
  name = "${name}-${version}";

  src = fetchurl {
    url = "https://github.com/wojdyr/xylib/releases/download/v${version}/${name}-${version}.tar.bz2";
    sha256 = "09j426qjbg3damch1hfw16j992kn2hj8gs4lpvqgfqdw61kvqivh";
  };

  buildInputs = [boost zlib bzip2 ];

  meta = {
    description = "Portable library for reading files that contain x-y data from powder diffraction, spectroscopy and other experimental methods";
    license = "LGPL";
    homepage = http://xylib.sourceforge.net/;
    platforms = stdenv.lib.platforms.linux;
  };
}
Add library: xylib 2014-08-13 23:13:12 +00:00			`{ stdenv, fetchurl, boost, zlib, bzip2 }:`

			`let`
			`name = "xylib";`
			`version = "1.3";`
			`in`
			`stdenv.mkDerivation {`
			`name = "${name}-${version}";`

			`src = fetchurl {`
			`url = "https://github.com/wojdyr/xylib/releases/download/v${version}/${name}-${version}.tar.bz2";`
			`sha256 = "09j426qjbg3damch1hfw16j992kn2hj8gs4lpvqgfqdw61kvqivh";`
			`};`

			`buildInputs = [boost zlib bzip2 ];`

			`meta = {`
Fix many package descriptions (My OCD kicked in today...) Remove repeated package names, capitalize first word, remove trailing periods and move overlong descriptions to longDescription. I also simplified some descriptions as well, when they were particularly long or technical, often based on Arch Linux' package descriptions. I've tried to stay away from generated expressions (and I think I succeeded). Some specifics worth mentioning: * cron, has "Vixie Cron" in its description. The "Vixie" part is not mentioned anywhere else. I kept it in a parenthesis at the end of the description. * ctags description started with "Exuberant Ctags ...", and the "exuberant" part is not mentioned elsewhere. Kept it in a parenthesis at the end of description. * nix has the description "The Nix Deployment System". Since that doesn't really say much what it is/does (especially after removing the package name!), I changed that to "Powerful package manager that makes package management reliable and reproducible" (borrowed from nixos.org). * Tons of "GNU Foo, Foo is a [the important bits]" descriptions is changed to just [the important bits]. If the package name doesn't contain GNU I don't think it's needed to say it in the description either. 2014-08-24 14:21:08 +00:00			`description = "Portable library for reading files that contain x-y data from powder diffraction, spectroscopy and other experimental methods";`
Add library: xylib 2014-08-13 23:13:12 +00:00			`license = "LGPL";`
			`homepage = http://xylib.sourceforge.net/;`
			`platforms = stdenv.lib.platforms.linux;`
			`};`
			`}`