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

[Mohammadreza Khellat]

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

                 Summary: Source code downloads and Job manager
                 Project: Reproducible paper template
            Submitted by: mkhellat
            Submitted on: Wed 01 May 2019 05:21:10 AM UTC
         Should Start On: Wed 01 May 2019 12:00:00 AM UTC
   Should be Finished on: Wed 01 May 2019 12:00:00 AM UTC
                Category: Software
                Priority: 7 - High
                  Status: Postponed
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00

    _______________________________________________________

Details:

The source code download issues are really annoying.

1. 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.


2. 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.

3. 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/