now users are expected to either install a binary deb package or use the build system directly when installing piscsi and the clients
create an INSTALL.md file with instructions how to use both the Makefile and Meson build systems
easyinstall.sh has been restructured to handle companion app installation solely, while the Netatalk installation script uses the Debian package instead of compiling from source
move the network configuration ASCII graphics over to the piscsi-network-profile script
Leveraging the Debian packaging allows us to preload more packages in the release image, while speeding up the initial pip install process when creating the venv
We also cut down on python package version upgrades maintenance overhead
Now the Web UI and OLED startup scripts are flagged to use system libraries when creating venvs
Refactor the deb packages to always separate backend and frontend packages,
then capture the error of a missing hfsutils (fell off Debian Trixie)
A future improvement would be to either build hfsutils from scratch,
or move to something like djjr
The python package caching has proven ineffectual, and this method of caching is now actually illegal in Raspbian Trixie (system python environment is externally managed to prevent dependency hell)
The script has a bunch of steps for renaming or removing user data originating in the era when the project was called RaSCSI
It's been 3 years now since the renaming to PiSCSI, so it's time to simplify the script
If someone needs to migrate old data, they should do an upgrade to an intermediate release first, and then to the latest release
The easyinstall script tries to do some clever git operations for every time you build piscsi to make sure you're always on the latest revision of your branch
However I think this is unintuitive and dangerous to do in a script; better to leave it up to the user to run git commands before easyinstall
It also makes it impossible to use the script when you're on a work branch that can't be fast forwarded to the remote state
Use the latest v4 release tarball to build, which can be installed on top of an older v2 installation
Removed the "cores" option since meson is much better at doing dynamic multi threaded compilation
Also, the netatalk webmin module installation is now part of the netatalk build system proper
* Dynamically detect an available network i/f, and abort if none is found
* Network i/f fallback for headless mode
* Split piscsi installation and system service configuration
- Inject piscsi_bridge into atalkd.conf if in use (#1088)
- Pass more parameters to the Netatalk script (cores, headless, no make clean, no packages)
- Bump to Netatalk 2.x 230202
Daniel Markstedt
BogDan Vatra
Daniel Markstedt
Delan Azabani
PiSCSI User
Uwe SeimetandFrank Danapfel
Benjamin Krein
Tony KukerandTony Kuker
