BSD Ports

devel/intervaltree 0.1.2 FreeBSD

Minimal C++ interval tree implementation

System
FreeBSD
Repository
FreeBSD ports
Maintainer
[email protected]
Last update
Commit
2414383046
License
MIT
Categories
devel
Package size
144.8 KiB, 408.9 KiB installed

Description

An interval tree can be used to efficiently find a set of numeric intervals overlapping or containing another interval. This library provides a basic implementation of an interval tree using C++ templates, allowing the insertion of arbitrary types into the tree.

In the other systems

SystemPortVersion
FreeBSDdevel/intervaltree0.1.2
DragonFlydevel/intervaltree0.1.2

Install

Binary package:

pkg install intervaltree

From the ports tree:

cd /usr/ports/devel/intervaltree/ && make install clean

To depend on this port in another port's Makefile:

RUN_DEPENDS=	intervaltree>0:devel/intervaltree

Packages

The version each package repository carries. “-” means the repository builds no package of it, “n/a” that there is no such repository.

Repositoryaarch64amd64armv6armv7i386
FreeBSD:14:latest0.1.20.1.2-0.1.20.1.2
FreeBSD:14:quarterly0.1.20.1.2n/a0.1.20.1.2
FreeBSD:15:latest0.1.20.1.2n/a0.1.20.1.2
FreeBSD:15:quarterly0.1.20.1.2n/an/an/a
FreeBSD:16:latest0.1.20.1.2n/an/an/a
FreeBSD:16:quarterlyn/an/an/an/an/a

Dependencies

The Makefile names none itself; they come from USES and USE_*.

The full lists below include those, and their dependencies in turn.

Required by 1

Configuration

No options to configure.

Service scripts
none

Files

distinfo 1
FileSizeSHA256
ekg-intervaltree-0.1-2-gaa59377_GH0.tar.gz725654813653eade9572ed39a70e578958ccce845506ef23f609f680040d92c1d8868

Commit history 1

DateCommitCreditsLog message
2414383046 Jason W. Bacon Release numerous ports to ports@
I've been retired for a few years, and it is unlikely I will be doing any more scientific computing support in the future. I have continued to maintain ~160 ports to the best of my ability, mainly as a favor to the community, but I can no longer justify the time and effort required. I am therefore releasing most of my scientific ports, along with a few others, to ports@. I will continue to maintain ports I am actively using and those for which I am upstream.