bug-wget
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-wget] [bug #47533] [RFE] consolidate metalink options


From: anonymous
Subject: [Bug-wget] [bug #47533] [RFE] consolidate metalink options
Date: Fri, 25 Mar 2016 15:42:19 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36

URL:
  <http://savannah.gnu.org/bugs/?47533>

                 Summary: [RFE] consolidate metalink options
                 Project: GNU Wget
            Submitted by: None
            Submitted on: Fri 25 Mar 2016 03:42:18 PM UTC
                Category: Feature Request
                Severity: 3 - Normal
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Dusty Mabe
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: None
        Operating System: None
         Reproducibility: None
           Fixed Release: None
         Planned Release: None
              Regression: None
           Work Required: None
          Patch Included: None

    _______________________________________________________

Details:


With [1] we would possibly have three options for metalink downloads:

--metalink - for urls that link to a metalink xml file 
--input-metalink - for local metalink files on local disk
--metalink-over-http - for urls that have metalink information in http
headers

I believe we could combine these all in to one option; --metalink.

Assuming wget --metalink $url is provided: 

If provided --metalink file:///path/to/file; then
   process metalink xml file and download target
else if http headers received from $url; then
   process http header metalink information and download target
else if target is xml metalink from $url
   process metalink xml file and download target
else (the $url does not reference a metalink)
   fallback to normal http download of target

We could deprecate the --input-metalink and --metalink-over-http options and
phase them out over time. Is this reasonable?

[1] https://savannah.gnu.org/bugs/index.php?47532




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47533>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]