Check --with-packages-download-dir option.
This is a 2 step process. For ex - the first step:
>>>
balay@sb /home/balay/petsc (master=)
$ ./configure --with-packages-download-dir=$HOME/tmp --download-metis
--download-parmetis
===============================================================================
Configuring PETSc to compile on your system
===============================================================================
Download the following packages to /home/balay/tmp
metis ['git://https://bitbucket.org/petsc/pkg-metis.git',
'https://bitbucket.org/petsc/pkg-metis/get/v5.1.0-p10.tar.gz']
parmetis ['git://https://bitbucket.org/petsc/pkg-parmetis.git',
'https://bitbucket.org/petsc/pkg-parmetis/get/v4.0.3-p6.tar.gz']
Then run the script again
<<<<
Satish
On Wed, 18 Nov 2020, Blaise A Bourdin wrote:
> Hi,
>
> I am working with a company whose cluster is an a private network without
> connectivity to the outside world. Our process to install petsc is to
> manually extract the packages URL from config/BuildSystem/packages/ and
> download the appropriate files.
> Another approach is to run configure and let it fail when it cannot download
> a package, note the download URL, and manually download it from a separate
> machine.
>
> Is there a quicker way to get the URL of all packages that will be downloaded
> without running through the whole configure process?
>
> Assuming that I know the list of package that I will want, is there a
> programmatic way to figure out what os the download URL for say Metis or
> sowing?
>
> Regards,
> Blaise
>
>
>
