libtnt 1.2.6-1.1 source package in Ubuntu
Changelog
libtnt (1.2.6-1.1) unstable; urgency=medium
* Non-maintainer upload.
* Refresh packaging.
* debian/control:
+ Bump debhelper compat to v13.
+ Bump Standards-Version to 4.5.1.
+ Use "Rules-Requires-Root: no".
+ Document homepage. (Closes: #615276)
* debian/rules: Use dh sequencer. (Closes: #395616)
+ Also do not call gzip and tar. (Closes: #777428)
* debian/docs: Directly install html docs.
-- Boyuan Yang <email address hidden> Sat, 02 Jan 2021 19:34:33 -0500
Upload details
- Uploaded by:
- Juan Esteban Monsalve Tobon
- Uploaded to:
- Sid
- Original maintainer:
- Juan Esteban Monsalve Tobon
- Architectures:
- all
- Section:
- math
- Urgency:
- Medium Urgency
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| libtnt_1.2.6-1.1.dsc | 1.7 KiB | 102c237545635fde6a44c4f2a5b9818cb282efe9a8a0b030042f9eda9915290c |
| libtnt_1.2.6.orig.tar.gz | 51.1 KiB | 016851ba0e263d160f42e81317ac5c9a1de4b93cc6b952c9c680857e01f4cddb |
| libtnt_1.2.6-1.1.debian.tar.xz | 9.4 KiB | 48bc0285d2f40c569b91ce1dfcbe2084d59ea83c935e4341596fe656c3ffe99a |
Available diffs
- diff from 1.2.6-1 (in Ubuntu) to 1.2.6-1.1 (11.4 KiB)
No changes file available.
Binary packages built by this source
- libtnt-dev: interface for scientific computing in C++
The Template Numerical Toolkit (TNT) is a collection of interfaces and
reference implementations of numerical objects useful for scientific
computing in C++. The toolkit defines interfaces for basic data
structures, such as multidimensional arrays and sparse matrices,
commonly used in numerical applications. The goal of this package is to
provide reusable software components that address many of the portability
and maintenance problems with C++ codes.
.
TNT provides a distinction between interfaces and implementations of TNT
components. For example, there is a TNT interface for two-dimensional
arrays which describes how individual elements are accessed and how
certain information, such as the array dimensions, can be used in
algorithms; however, there can be several implementations of such an
interface: one that uses expression templates, or one that uses BLAS
kernels, or another that is instrumented to provide debugging information.
By specifying only the interface, applications codes may utilize such
algorithms, while giving library developers the greatest flexibility in
employing optimization or portability strategies.
