libbytesize 1.2-1build1 source package in Ubuntu
Changelog
libbytesize (1.2-1build1) bionic; urgency=medium * No-change rebuild for mpfr soname change. -- Matthias Klose <email address hidden> Wed, 24 Jan 2018 21:23:49 +0000
Upload details
- Uploaded by:
- Matthias Klose
- Uploaded to:
- Bionic
- Original maintainer:
- Utopia Maintenance Team
- Architectures:
- any
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
libbytesize_1.2.orig.tar.gz | 68.9 KiB | 20b91adcb216b1cdc99ade5cfa953cd3e10f848ec21436df2fd68f6437c7b744 |
libbytesize_1.2-1build1.diff.gz | 2.4 KiB | 7a9109dde1ad3864ba5428931a574e8deb1de3e64330378d9a2858e15e12d321 |
libbytesize_1.2-1build1.dsc | 2.2 KiB | 25dc0f4436d344707e5c7b24bbfaf3ec17dd7f47fee04b0ea3dc4c140f89f1f4 |
Available diffs
- diff from 1.2-1 (in Debian) to 1.2-1build1 (268 bytes)
Binary packages built by this source
- libbytesize-dev: library for common operations with sizes in bytes - development
This package ships the header pkg-config files needed for building things
against the libbytesize library.
- libbytesize1: library for 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:
.
* How to get a human-readable string for the given size?
* How to store the given size so that no significant information is lost?
* If we store the size in bytes, what if the given size gets over the
MAXUINT64 value? How to interpret sizes entered by users according
to their locale and typing conventions?
* How to deal with the decimal/binary units (MB vs. MiB) ambiguity?
.
This library aims to be as much generally usable as possible, small, fast and
be easily interfaced from other languages.
- libbytesize1-dbgsym: debug symbols for libbytesize1
- python3-bytesize: Python 3 bindings for libbytesize
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:
.
* How to get a human-readable string for the given size?
* How to store the given size so that no significant information is lost?
* If we store the size in bytes, what if the given size gets over the
MAXUINT64 value? How to interpret sizes entered by users according
to their locale and typing conventions?
* How to deal with the decimal/binary units (MB vs. MiB) ambiguity?
.
This library aims to be as much generally usable as possible, small, fast and
be easily interfaced from other languages.
.
This package contains bindings for libbytesize in Python3.