[Reproduce-devel] [task #15262] Source code downloads and Job manager

[Mohammadreza Khellat]

Follow-up Comment #2, task #15262 (project reproduce):

You see the complication comes from the hosting web-server. 
In other words, for different servers, you might need to use a different
command. 

The logical method is to use git repo itself; and use git commands. So i
suggest we do this:

* Instead of downloading one-by-one, lets put all the required tar balls in a
git repo and then download it at the start of the configure script using git
commands. However, yet I need to figure out the optimized way of updating the
downloaded git repo later on.

* After the download is done, the rest could happen as it is normally
happening in the configure script.

----

And here is the main msg, so you would be happy ;) and it would look nicer:

The source code download issues are really annoying.

* Only https links should be used (no ftp no http). It should be understood
that web servers might have different security configurations and the best way
to download files from them would be through modern web-browsers unless they
have provided and documented specific wget and curl commands as part of their
documentation. Here is the wget equivalent command of downloading libffi
through mozilla firefox 65.0:

wget --header 'Host: gcc.gnu.org' --user-agent 'Mozilla/5.0 (X11; Linux
x86_64; rv:65.0) Gecko/20100101 Firefox/65.0' --header 'Accept:
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8'
--header 'Accept-Language: en-US,en;q=0.5' --referer
'https://gcc.gnu.org/pub/libffi/' --header 'DNT: 1' --header
'Proxy-Authorization: Basic
Lmh4QDQ2MjI5NDtpci46Nnp4SStsYzhmYldORXZmZnZXMlg3ZVlUTGhFSkpNRFljOHFHeDdNVnY4RT0='
--header 'Upgrade-Insecure-Requests: 1'
'https://gcc.gnu.org/pub/libffi/libffi-3.2.1.tar.gz' --output-document
'libffi-3.2.1.tar.gz'









So, I could say downloading packages using wget is not the best option.

* There should be 3 reties and at the end, the user should be informed to
download the package manually, and the script should exit. The job manager
should be configured in a way that configure script should continue the job
from where it was hanging not from a random new place.

* The other option is that all the required packages be hosted on a separate
git repo. This would be quite standard because at least we know that the pkgs
are accessible through the same method through which the main source code was
accessible.

    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?15262>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/