[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#31999] [PATCH 3/7] gnu: Add libbytesize.
From: |
Pierre Neidhardt |
Subject: |
[bug#31999] [PATCH 3/7] gnu: Add libbytesize. |
Date: |
Thu, 28 Jun 2018 23:35:23 +0200 |
* gnu/package/c.scm (libbytesize): New variable.
---
gnu/packages/c.scm | 75 ++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 75 insertions(+)
diff --git a/gnu/packages/c.scm b/gnu/packages/c.scm
index bc6042874..0398bb04d 100644
--- a/gnu/packages/c.scm
+++ b/gnu/packages/c.scm
@@ -2,6 +2,7 @@
;;; Copyright © 2016, 2018 Ludovic Courtès <address@hidden>
;;; Copyright © 2016, 2017 Ricardo Wurmus <address@hidden>
;;; Copyright © 2018 Tobias Geerinckx-Rice <address@hidden>
+;;; Copyright © 2018 Pierre Neidhardt <address@hidden>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -22,6 +23,7 @@
#:use-module ((guix licenses) #:prefix license:)
#:use-module (guix packages)
#:use-module (guix download)
+ #:use-module (guix git-download)
#:use-module (guix build-system gnu)
#:use-module (guix build-system trivial)
#:use-module (gnu packages bootstrap)
@@ -30,6 +32,12 @@
#:use-module (gnu packages perl)
#:use-module (gnu packages texinfo)
#:use-module (gnu packages guile)
+ #:use-module (gnu packages multiprecision)
+ #:use-module (gnu packages pcre)
+ #:use-module (gnu packages python)
+ #:use-module (gnu packages autotools)
+ #:use-module (gnu packages gettext)
+ #:use-module (gnu packages pkg-config)
#:use-module (srfi srfi-1))
(define-public tcc
@@ -166,3 +174,70 @@ compiler while still keeping it small, simple, fast and
understandable.")
;; PCC incorporates code under various BSD licenses; for new code bsd-2 is
;; preferred. See http://pcc.ludd.ltu.se/licenses/ for more details.
(license (list license:bsd-2 license:bsd-3))))
+
+(define-public libbytesize
+ (package
+ (name "libbytesize")
+ (version "1.3")
+ (source (origin
+ (method git-fetch)
+ (uri (git-reference
+ (url "https://github.com/storaged-project/libbytesize")
+ (commit version)))
+ (file-name (string-append name "-" version "-checkout"))
+ (sha256
+ (base32
+ "1ys5d8rya8x4q34gn1hr96z7797s9gdzah0y0d7g84x5x6k50p30"))))
+ (build-system gnu-build-system)
+ (native-inputs
+ `(("autoconf" ,autoconf)
+ ("automake" ,automake)
+ ("libtool" ,libtool)
+ ("gettext" ,gettext-minimal)
+ ("pkg-config" ,pkg-config)
+ ("python" ,python)
+ ("python2" ,python-2) ; For tests.
+ ("python2-six" ,python2-six) ; For tests.
+ ("python2-polib" ,python2-polib) ; For tests.
+ ))
+ (inputs
+ `(("mpfr" ,mpfr)
+ ("pcre" ,pcre)))
+ (arguments
+ `(#:tests? #f ; One test fails because busctl (systemd only?) and
+ ; python2-pocketlint are missing.
+ #:phases
+ (modify-phases %standard-phases
+ (add-after 'unpack 'autogen
+ (lambda _
+ (invoke ("sh" "autogen.sh")))))))
+ (home-page "https://github.com/storaged-project/libbytesize")
+ (synopsis "Tiny C library for working with arbitrary big sizes in bytes")
+ (description
+ "The goal of this project is to provide a tiny library that would
+facilitate the common operations with sizes in bytes. Many projects need to
+work with sizes in bytes (be it sizes of storage space, memory...) and all of
+them need to deal with the same issues like:
+
address@hidden
address@hidden How to get a human-readable string for the given size?
address@hidden How to store the given size so that no significant information
is lost?
address@hidden If we store the size in bytes, what if the given size gets over
the
+MAXUINT64 value?
address@hidden How to interpret sizes entered by users according to their
locale and
+typing conventions?
address@hidden How to deal with the decimal/binary units (MB vs. MiB) ambiguity?
address@hidden itemize
+
+Some projects have all the above questions/concerns addressed well, some have
+them addressed partially some simply don't care. However, having (partial)
+solutions implemented in multiple places every time with a different set of
+bugs, differences in behaviour and this or that missing is a waste of time and
+effort. We need a generally usable solution that could be used by every
+project that needs to deal with sizes in bytes.
+
+Since the goal is to provide a solution as much generally usable as possible
+the implementation has to be small, fast and written in a language that can be
+easily interfaced from other languages. The current obvious choice is the C
+language with thin bindings for other languages.")
+ (license license:lgpl2.1+)))
--
2.17.1