"make install" installs source-level tools to the system

[paravoid]

"make install" seems to be installing all of the files under "tools" to (e.g.) /usr/share/ipv6calc/tools.

However, most of these seem to be internal, source-level tools, e.g. regenerating header files out of IEEE databases and such, and are not really useful in the "destionation" system or in /usr.

A real-world problem that arises with this is when building ipv6calc for a distribution, such as Debian.

[pbiering]

@paravoid : will there be any other script installed than

DBIP-update.sh
GeoIP-update.sh
IP2Location-update.sh
ipv6calc-create-registry-list-ipv4.pl
ipv6calc-create-registry-list-ipv6.pl
ipv6calc-create-update-ipset.sh
ipv6calc-db-update.sh
ipv6calc-registries-check-run-create.sh
ipv6calc-update-registries.sh

because all of them are required to update or create DB files after install.

Scripts which are only used during internal hardcoded database updates are not packaged to my knowledge:

ls -1 databases/tools/
create_ieee_headerfile.pl
ipv6calc-db-info.pl
test_db_lookup.sh

[paravoid]

I see, my mistake. I saw the calls from databases/ipv4-assignment/Makefile, and was quick to assume this is for generating header files. As I understand it now, these tools can also generate source-level headers (by passing -H), as the build system does, but they can also generate BerkeleyDB files, to be used by the already-built (with --enable-external) ipv6calc. Did I get this right?

[pbiering]

Did I get this right?

Yes, some internal databases can be superseeded by local "external" databases.