So far as I know you need to run JetPack once with everything connected and working (originally the manifest from the partial run on a non-Ubuntu system worked, but this leaves out some content which has changed since this was originally written). This is how the current manifest gets downloaded. Once you have a valid manifest which is updated it should work to use those URLs without an Ubuntu host (you could even use wget from the Jetson).
Keep in mind that one of the major reasons for using JetPack is due to the complicated dependencies. If you have a log of an install to view install order from, then you will have a lot less trouble.
If you have an already installed set of software on a Jetson from JetPack 3.3, then you could just copy the “/var/cuda-repo-whatever/” to get the “.deb” files. Other content going into “/etc/apt/” allows “apt-get” to see the content of “/var/cuda-repo-whatever/” for automatic use without manually adding a “.deb” package manually using “dpkg”.
For automating there are a lot of ways to do this once you have the manifest. You could also make a script to basically copy the right parts from a clone…and then if the clone is updated the future copies would also be updated.
Can you give more details of how you want this to work and how you might want it to evolve over time?