debfiles if the other machine's package manager is known to be working.
deb approach is likely best for
tetex (and software that depends on it such as some versions of
lilypond), as the maintenance this performs at installation time is not usually reflected in its file lists; you might get errors like can't find the format file if you try to run it without a proper installation. There might be other packages like this too.
If you know for sure that certain versions of certain files will be available (because it will be a fresh installation, or because you've collected the data on your last visit), a list of these files and their timestamps can be provided so that the script will omit them; you can obtain such a list by entering find /[belorsuv]* -type f -print0 | xargs -0 ls --full-time > existing-files on the target machine (or on a local non-network installed copy of the fresh installation you plan).
If the machine will later be connected to the Internet in your absence, it might be easier to install some kind of remote administration. Perhaps the simplest way to do this (which does not require setting up SSH servers, open ports or persistent connections) is to set root's crontab to fetch commands from an HTTPS server you have an account on, e.g. echo "@reboot wget -q -O - https://example.org/example.txt | bash" | sudo crontab - (this will replace the existing crontab)---not suitable for very old Wget versions that did not check HTTPS certificates, but the last one of those was the 1.09 release in 2005's Debian Sarge.
Usual disclaimers apply (I hope the above is useful, but it's used at your own risk).