Port details |
- iprange Manage IP ranges
- 1.0.4_2 net-mgmt =3 1.0.4_2Version of this port present on the latest quarterly branch.
- Maintainer: garga@FreeBSD.org
- Port Added: 2017-05-08 10:49:49
- Last Update: 2024-01-16 14:02:42
- Commit Hash: 08a9c4d
- People watching this port, also watch:: bingrep, check_ssl_cert, newsboat, xrdp, pcpustat
- License: GPLv2+
- WWW:
- https://github.com/firehol/iprange
- Description:
- This tool is capable of managing sets of IPs.
Why to use iprange over any other aggregate ?
* simpler
* supports many input formats, all together in the same file
* faster, actually a lot faster (thanks to the original design
by Gabriel Somlo)
* can compare files with IPs to find if they overlap and to what degree
* can find the IPs common to a set of files
* can exclude IPs (merge a set of files while excluding all IPs matched
by another set of files)
- ¦ ¦ ¦ ¦
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- iprange>0:net-mgmt/iprange
- To install the port:
- cd /usr/ports/net-mgmt/iprange/ && make install clean
- To add the package, run one of these commands:
- pkg install net-mgmt/iprange
- pkg install iprange
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: iprange
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1538075765
SHA256 (iprange-1.0.4.tar.xz) = e138d18974fb65674e5ea53da1ffbdde19704208e5114cc6b32d01db3ce1d567
SIZE (iprange-1.0.4.tar.xz) = 104336
Packages (timestamps in pop-ups are UTC):
- This port has no dependencies.
- There are no ports dependent upon this port
Configuration Options:
- No options to configure
- Options name:
- net-mgmt_iprange
- USES:
- tar:xz
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 8
Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
Commit | Credits | Log message |
1.0.4_2 16 Jan 2024 14:02:42 |
Renato Botelho (garga) |
*/*: Restore GNU_CONFIGURE on my ports
I made a mistake and changed these ports to HAS_CONFIGURE when working
on MANPREFIX sanitization. Restore proper macro usage and set
GNU_CONFIGURE_MANPREFIX properly to keep manpages installed under
${PREFIX}/share.
Reported by: danfe
Sponsored by: Rubicon Communications, LLC ("Netgate") |
1.0.4_1 15 Jan 2024 21:37:38 |
Renato Botelho (garga) |
net-mgmt/iprange: Move manpages to ${PREFIX}/share
Sponsored by: Rubicon Communications, LLC ("Netgate") |
07 Sep 2022 21:58:51 |
Stefan Eßer (se) |
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner) |
1.0.4 07 Sep 2022 21:10:59 |
Stefan Eßer (se) |
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above ) |
1.0.4 07 Apr 2021 08:09:01 |
Mathieu Arnold (mat) |
One more small cleanup, forgotten yesterday.
Reported by: lwhsu |
1.0.4 06 Apr 2021 14:31:07 |
Mathieu Arnold (mat) |
Remove # $FreeBSD$ from Makefiles. |
1.0.4 27 Sep 2018 19:18:56 |
garga |
Update net-mgmt/iprange to 1.0.4
Sponsored by: Rubicon Communications, LLC (Netgate) |
1.0.3 08 May 2017 10:49:40 |
garga |
Add net-mgmt/iprange
This tool is capable of managing sets of IPs.
Why to use iprange over any other aggregate ?
* simpler
* supports many input formats, all together in the same file
* faster, actually a lot faster (thanks to the original design
by Gabriel Somlo)
* can compare files with IPs to find if they overlap and to what degree
* can find the IPs common to a set of files
* can exclude IPs (merge a set of files while excluding all IPs matched
by another set of files)
WWW: https://github.com/firehol/iprange
MFH: 2017Q2
Sponsored by: Rubicon Communications (Netgate) |
Number of commits found: 8
|