[PATCH] distro: Add GNU Libidn.

[PATCH] distro: Add GNU Libidn.

[Andreas Enge]

[-- Attachment #1.1: Type: text/plain, Size: 379 bytes --]

Another leaf package for the dependencies of gnunet...

I am still not clear whether we should do one package or more per file. I 
am tending more and more towards one package, one file, after trying to put 
cyrus-sasl with its dependencies into one file and ending up with openssl, 
mit-kerberos5 and cyrus-sasl all together.

So here one small file with one package.

Andreas


[-- Attachment #1.2: Type: text/html, Size: 2044 bytes --]

[-- Attachment #2: 0004-distro-Add-GNU-Libidn.patch --]
[-- Type: text/x-patch, Size: 3363 bytes --]

From 7d5d6c361ea12b4f985c10b10b44e9a3a1eddcef Mon Sep 17 00:00:00 2001
From: Andreas Enge <andreas@enge.fr>
Date: Sat, 29 Dec 2012 21:29:03 +0100
Subject: [PATCH 4/4] distro: Add GNU Libidn.

* distro/packages/libidn.scm: New file.
* Makefile.am (MODULES): Add it.
---
 Makefile.am                |    1 +
 distro/packages/libidn.scm |   51 ++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 52 insertions(+)
 create mode 100644 distro/packages/libidn.scm

diff --git a/Makefile.am b/Makefile.am
index 7bcc905..b209bca 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -71,6 +71,7 @@ MODULES =					\
   distro/packages/ld-wrapper.scm		\
   distro/packages/less.scm			\
   distro/packages/libffi.scm			\
+  distro/packages/libidn.scm			\
   distro/packages/libsigsegv.scm		\
   distro/packages/libunistring.scm		\
   distro/packages/libusb.scm			\
diff --git a/distro/packages/libidn.scm b/distro/packages/libidn.scm
new file mode 100644
index 0000000..e5f0a8d
--- /dev/null
+++ b/distro/packages/libidn.scm
@@ -0,0 +1,51 @@
+;;; Guix --- Nix package management from Guile.         -*- coding: utf-8 -*-
+;;; Copyright (C) 2012 Andreas Enge <andreas@enge.fr>
+;;;
+;;; This file is part of Guix.
+;;;
+;;; Guix 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.
+;;;
+;;; Guix 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 Guix.  If not, see <http://www.gnu.org/licenses/>.
+
+(define-module (distro packages libidn)
+  #:use-module (distro)
+  #:use-module (guix licenses)
+  #:use-module (guix packages)
+  #:use-module (guix download)
+  #:use-module (guix build-system gnu))
+
+(define-public libidn
+  (package
+   (name "libidn")
+   (version "1.26")
+   (source (origin
+            (method url-fetch)
+            (uri (string-append "mirror://gnu/libidn/libidn-" version
+                                ".tar.gz"))
+            (sha256 (base32
+                     "0g657kv60rh486m7bwyp5k24ljmym4wnb8nmk6d3i3qgr1qlqbqa"))))
+   (build-system gnu-build-system)
+;; FIXME: No Java and C# libraries are currently built.
+   (synopsis "GNU Libidn, a library to encode and decode internationalised domain names")
+   (description
+    "GNU Libidn is a fully documented implementation of the Stringprep,
+Punycode and IDNA specifications. Libidn's purpose is to encode and decode
+internationalised domain names.
+
+The library contains a generic Stringprep implementation. Profiles for
+Nameprep, iSCSI, SASL, XMPP and Kerberos V5 are included. Punycode and
+ASCII Compatible Encoding (ACE) via IDNA are supported. A mechanism to
+define Top-Level Domain (TLD) specific validation tables, and to compare
+strings against those tables, is included.
+Default tables for some TLDs are also included.")
+   (license lgpl2.1+)
+   (home-page "http://www.gnu.org/software/libidn/")))
-- 
1.7.10.4

Re: [PATCH] distro: Add GNU Libidn.

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> I am still not clear whether we should do one package or more per file. I 
> am tending more and more towards one package, one file, after trying to put 
> cyrus-sasl with its dependencies into one file and ending up with openssl, 
> mit-kerberos5 and cyrus-sasl all together.

Yeah.  The difficulty with several packages per file is that we may
quickly end up with circular dependencies among modules, which should be
avoided.

For strongly connected components of the DAG, like autotools.scm and
multiprecision.scm, it’s safe to bundle them together.  Likewise for
packages that have a common dependency, such as guile.scm.

> From 7d5d6c361ea12b4f985c10b10b44e9a3a1eddcef Mon Sep 17 00:00:00 2001
> From: Andreas Enge <andreas@enge.fr>
> Date: Sat, 29 Dec 2012 21:29:03 +0100
> Subject: [PATCH 4/4] distro: Add GNU Libidn.
>
> * distro/packages/libidn.scm: New file.
> * Makefile.am (MODULES): Add it.

Applied, thanks!

Ludo’.