Continuing FC vs ThemWi software clean-up

[Mychaela Falconia]

Hello FC and ThemWi community,

Past the finished release of new gsm-codec-lib, I am continuing the
cleanup of our code base, working toward a cleaner separation of what
is FreeCalypso vs what is Themyscira Wireless.  The following Hg
repositories have been moved over to ThemWi side and updated to use
the new ./configure system with freely changeable install location:

https://www.freecalypso.org/hg/gsm-codec-lib/
https://www.freecalypso.org/hg/rtp-debug-utils/
https://www.freecalypso.org/hg/sipout-test-utils/
https://www.freecalypso.org/hg/sms-coding-utils/
https://www.freecalypso.org/hg/themwi-nanp/
https://www.freecalypso.org/hg/themwi-ota-tools/

With the exception of gsm-codec-lib, all others are experimental or
developer-use-only or "rolling release" software, without formal point
releases.  Furthermore, one Hg repository had to be renamed: back in
2021 I created a little "playpen" repository named fc-ota-tools, for
playing with the OTA programming feature on Sysmocom (U)SIM cards, but
that function is 100% ThemWi rather than FreeCalypso, hence I renamed
the repo.  Obviously such renames can be very disruptive (and would be
if that sw were more actively used) and need to be kept to a minimum,
but in this case this specific Hg repo was clearly in the wrong
grouping - except that back in 2021-Feb I had not yet started using
Themyscira branding for work on the network side of GSM...

Past these changes, the primary remaining pain point is that on the
FreeCalypso side of the fence, all host sw still requires the fixed
install location under /opt/freecalypso.  However, there are two major
points about this fixed install location that are in need of periodic
reminders:

1) If we were following FHS, all of our specialized, not-Linux-generic
paths that are currently under /opt/freecalypso would be under
/usr/local/share/freecalypso instead - a lot more typing.  Furthermore,
they would move from /usr/local/share/freecalypso to /usr/share/freecalypso
any time any individual user switches from "build from source and
directly install" paradigm to "make distro packages" paradigm - and
having different paths for different users, for files that belong to FC
private fiefdom and have nothing whatsoever to do with general Unix/Linux
world, would be inordinate pain.  Plus having this fixed path allows
us to hard-code it in bazillion places without worrying about breakage.

2) For the one part of /opt/freecalypso tree that is visible to
"external" users, namely the binaries installed in /opt/freecalypso/bin,
the simplest solution for bringing them in line with ordinary user
expectations is to make symlinks from /usr/bin or /usr/local/bin or
wherever, pointing to the real binaries in /opt/freecalypso/bin.  This
approach is the officially recommended one, and recent releases of FC
sw components include an Installed-binaries manifest file that should
simplify automated generation of these symlinks.

So what are the remaining problems with /opt/freecalypso, if any?

Hasta la Victoria, Siempre,
Mychaela aka The Mother