I'm not quite sure what you mean with reference to the "system package manager." I find no GUI equivalent of Ubuntu's "synaptic package manager." I prefer to get things done on the command line with *nix. ... I wonder if you mean something like dpkg. ... sudo apt-get install libnet-ssleay-perl ... Would this be an instance of using the "system package manager," as you mean it?

The system package manager is the Advanced Package Tool on Debian-based systems like Ubuntu and Raspbian, and the RPM Package Manager on RedHat-based systems. Synaptic is just a frontend for APT and dpkg is one of the lower-level tools used by APT. Using APT from the commandline is done with the apt* commands, so yes, the apt-get command is what I meant. I personally often use the aptitude frontend for package management from the command line.

I do have a sticky wicket, where I can't get cpanm to find dependencies: ... Configuring . failed. See /home/pi/.cpanm/work/1647208802.16932/build.log for details.

You'd have to look into that file for the actual error message and let us know what it is. I might suspect a missing dependency on a lower level than Perl modules, e.g. a C library.

I herded the requires into a barebones module in its own directory. I don't know how to serve it up any better than that.(?)

Your requires1.pm would typically be called cpanfile and not start with a package statement. See cpanfile and the corresponding discussion in your thread Using Cartons to automate module installs.

I couldn't get cpanm to find modules in typical perl .pl scripts

You might be interested in lazy, though as the name implies, this shouldn't be your package management solution of choice.

Regarding section 5, Crontab to broadcast RPi's address and name, What is the purpose of doing this? Would this cause you to be indexed by search engines, or is it all within 50 yards

UDP broadcasts are usually not forwarded by routers, especially not to the Internet, so this should stay within the local network. On some (nowadays many) local networks, the router is smart enough to add a local DNS entry so the RPi can be reached by its hostname. On other networks, this may not be available, so there, this UDP broadcast simply serves for me to discover the IP that the RPi has been assigned. I broadcast the hostname so that I can keep multiple RPi apart (which is why it's a good idea to change the default hostname).

Update: The background for this is that I prefer a headless setup of my RPis, purely over the network, which is why my notes include instructions on how to enable WiFi and the ssh server. There is a small security risk in not changing the password from the default before the first boot, perhaps I will update my notes in that regard. Update 2: Done. Also, BitBucket wasn't rendering some of the Markdown correctly, which should now be fixed, so those crontab lines you quoted should be readable on the site now (when in doubt, refer to the source). /Update

Can you break this up into parts

I'm basicially just sending the hostname in a UDP broadcast packet, where the socat commandline is what I looked up for that purpose, I'm not an socat expert :-) The crontab entries cause that to happen every minute, plus one extra time at boot, and I do 2>/dev/null so I don't get tons of emails from the cron daemon.