The Prefix WhoIs Project provides a whois-compatible client and server
framework for disclosing various up-to-date routing information.
Instead of using registrar-originated network information (which is often
unspecific or inaccurate), Prefix WhoIs uses the Internet's global routing
table as gleaned from a number of routing peers around the world. Other
sources of information, such as imported data from ARIN are also supported
(a separate agreement with ARIN is required).
This port requires additional tasks before it will function properly.
1. Create and initialize the database:
mysql> create database pwhois;
mysql> create user 'pwhois'@'localhost' identified by 'secret-password';
mysql> grant all privileges on pwhois.* to 'pwhois'@'localhost';
mysql> use pwhois;
mysql> \. /usr/local/share/pwhois/createdb.sql
2. Edit /usr/local/etc/pwhois/pwhoisd.conf and update:
* Database connection information
* RouteView servers (some may be slower than others)
3. Populate the database with data for the first time by running:
/usr/local/sbin/pwhois-updatedb
4. Add the following to /etc/rc.conf:
pwhoisd_enable="YES"
5. Start pwhoisd for the first time by running:
service pwhoisd start
6. To enable daily updates, edit /etc/periodic.conf and add:
daily_pwhois_updatedb_enable="YES"
databases/p5-DBD-mysql: Fix for MariaDB users
Add a new variable DBD_MYSQL, use that in *_DEPENDS and add mysql to USES
where required. DBD_MYSQL will automatically set the correct DBD dependency.
In cd16748194e2 databases/p5-DBD-mysql was updated to 5.x, in 5.x the
support for MariaDB was removed and only MySQL >= 8.0 is supported.
In the 4.x releases MariaDB is still supported, according to upstream 4.x
will still be supported for a while [1], so use that for now when we detect
that MYSQL_FLAVOUR is set to mariadb. databases/p5-DBD-mysql4 was added in
d95f49cb3b54.
DBD:MariaDB would be another alternative, but migrating to it might need
more analysis than just staying with the 4.x releases of p5-DBD-mysql. This
(Only the first 15 lines of the commit message are shown above )
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)
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 )
net: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* <ports@c0decafe.net>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Straup Cope <ascope@cpan.org>
* Aaron Zauner <az_mail@gmx.at>
* Adam Jette <jettea46@yahoo.com>
* Adam Weinberger <adamw@FreeBSD.org>
* Alan Eldridge <alane@geeksrus.net>
* Alex Bakhtin <Alex.Bakhtin@gmail.com>
* Alex Deiter <Alex.Deiter@Gmail.COM>
* Alex Dupre <ale@FreeBSD.org>
* Alex Dupre <sysadmin@alexdupre.com>
(Only the first 15 lines of the commit message are shown above )
When there is a do-install target, do not use a post-install target, do
everything at once. Sometime, rename post-install into a options helper
target.
I did not fix ports that were such a mess that I could not figure out
what they really wanted to do. I also did not change ports that had
some version of an auto-plist code in post-install, for the same reason.
With hat: portmgr
Sponsored by: Absolight
New port: net/pwhois:
The Prefix WhoIs Project provides a whois-compatible client and server
framework for disclosing various up-to-date routing information.
Instead of using registrar-originated network information (which is often
unspecific or inaccurate), Prefix WhoIs uses the Internet's global routing
table as gleaned from a number of routing peers around the world. Other
sources of information, such as imported data from ARIN are also supported
(a separate agreement with ARIN is required).
WWW: http://pwhois.org/