Re: recipe for gettext master

[Rob Vermaas]

Hi,

I have created a jobset for gettext master branch, you can see the results at: http://hydra.nixos.org/jobset/gnu/gettext-master

 

 . I have committed the release.nix to http://savannah.gnu.org/projects/hydra-recipes/

 

Currently the builds fail as the tarball that is built in tarball job seems empty?

Cheers,

Rob

On Thu, Dec 20, 2012 at 12:29 AM, Daiki Ueno <address@hidden> wrote:

Hi,

The attached is a Hydra recipe for gettext git master (based on hello).
I tested it locally with nix-build and confirmed that "tarball" and
"build" successfully complete on "x86_64-linux" system.

Could you consider providing the build on hydra.nixos.org?  I'm new to
the Nix language so reviews/fixes would be appreciated.

Thanks,
--
Daiki Ueno

/* Continuous integration of GNU with Hydra/Nix.
   Copyright (C) 2012  Rob Vermaas <address@hidden>
   Copyright (C) 2012  Daiki Ueno <address@hidden>

   This program is free software: you can redistribute it and/or modify
   it under the terms of the GNU General Public License as published by
   the Free Software Foundation, either version 3 of the License, or
   (at your option) any later version.

   This program is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
   GNU General Public License for more details.

   You should have received a copy of the GNU General Public License
   along with this program.  If not, see <http://www.gnu.org/licenses/>.  */

{ nixpkgs ? <nixpkgs>
, gettext ? { outPath = <gettext>; }
}:

let
  pkgs = import nixpkgs {};

  meta = {
    homepage = http://www.gnu.org/software/gettext/;

    description = "GNU gettext, a well integrated set of translation tools and documentation";

    longDescription = ''
      Usually, programs are written and documented in English, and use
      English at execution time for interacting with users.  Using a
      common language is quite handy for communication between
      developers, maintainers and users from all countries.  On the
      other hand, most people are less comfortable with English than
      with their own native language, and would rather be using their
      mother tongue for day to day's work, as far as possible.  Many
      would simply love seeing their computer screen showing a lot
      less of English, and far more of their own language.

      GNU `gettext' is an important step for the GNU Translation
      Project, as bit is an asset on which we may build many other
      steps. This package offers to programmers, translators, and even
      users, a well integrated set of tools and
      documentation. Specifically, the GNU `gettext' utilities are a
      set of tools that provides a framework to help other GNU
      packages produce multi-lingual messages.
    '';

    # some files are under GPLv2+ and LGPL
    license = "GPLv3";

    maintainers = [
      "Daiki Ueno <address@hidden>"
    ];
  };
in
  import ../gnu-jobs.nix {
    name = "gettext";
    src  = gettext;
    inherit nixpkgs meta;
    enableGnuCrossBuild = true;

    customEnv = {
      tarball = pkgs: {
        autoconfPhase = ''
          export GNULIB_TOOL="../gnulib/gnulib-tool"
          ./autogen.sh
          # archive.dir.tar is not under version control; use empty
          # tarball for building
          : > dummy
          tar cf gettext-tools/misc/archive.dir.tar dummy
          rm -f dummy
        '';
        dontBuild = false;
        buildInputs = with pkgs; [
          bison
          gettext_0_18 # needed for bootstrap
          git
          gperf
          help2man
          perl
          texinfo
          wget
        ];
      };
    };
  }

--
Rob Vermaas

[email] address@hidden