<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class="">I'm pretty sure it uses the system-provided curl. And again, am very happy about that. <br class=""></blockquote><br class="">TL does not provide curl, it needs to be provided by the system. But it<br class="">is not necessary.<br class=""></div></div></blockquote><div><br class=""></div><div>Not necessary in what sense? If LWP works, then nothing else is needed. If it doesn’t work (for whatever reason), then reverting to what’s installed on the target system seems a reasonable fallback.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class=""> THis is *really* surprising... WHY did it choose wget from the system,<br class=""> it should have taken the one provided by TL ... I need to find out why.<br class=""><br class="">Can you please make an option for the user to force using the system-provided wget? Pretty-please?<br class=""></blockquote><br class="">What for? </div></div></blockquote><div><br class=""></div><div>So it would work (a) on systems like mine, and (b) with the current web servers that now usually insist on https, and often rewrite the URL switching to https: on their own.</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">On Mac it will probably never hit wget anymore. With the<br class="">latest update you included, the logic is now<br class=""> - by default try LWP<br class=""> - if that fails and curl is available, try curl<br class=""> - if that fails, use wget<br class=""></div></div></blockquote><div><br class=""></div>But which wget? The one that’s shipped with TL doesn’t cut the mustard.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="">Now since curl is always available on MacOS, I guess that wget will<br class="">never be used on.<br class=""></div></div></blockquote><div><br class=""></div><div>You may be right in this. Still, I see no harm in allowing for wget - some installations may have curl broken. I know it took me some time to get it working, and it wasn’t a high priority because wget was there, doing the job.</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">And, in addition, there is already a way to force TL to use<br class="">different programs. I quote from the tlmgr man page:<br class=""><br class=""> "TEXLIVE_DOWNLOADER"<br class=""> "TL_DOWNLOAD_PROGRAM"<br class=""> “TL_DOWNLOAD_ARGS"<br class=""></div></div></blockquote><div><br class=""></div><div>Ah. I wouldn’t be able to use these with TeX Live Utility, but they should work with tlmgr?</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""> These options allow selecting different download programs then the<br class=""> ones automatically selected by the installer. The order of selection<br class=""> is:<br class=""><br class=""> 1. If the environment variable "TEXLIVE_DOWNLOADER" is defined,<br class=""> use it; abort if the specified program doesn't work. Possible<br class=""> values: "curl", "wget". The necessary options are added<br class=""> internally.<br class=""></div></div></blockquote><div><br class=""></div>What about path? What if a system has more than one wget or curl installed? E.g.,</div><div><br class=""></div><div><div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family: "Andale Mono"; color: rgb(40, 254, 20); background-color: rgba(0, 0, 0, 0.901961);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">$ type -all curl</span></div><div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family: "Andale Mono"; color: rgb(40, 254, 20); background-color: rgba(0, 0, 0, 0.901961);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">curl is /opt/local/bin/curl</span></div><div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family: "Andale Mono"; color: rgb(40, 254, 20); background-color: rgba(0, 0, 0, 0.901961);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">curl is /usr/bin/curl</span></div><div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family: "Andale Mono"; color: rgb(40, 254, 20); background-color: rgba(0, 0, 0, 0.901961);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">$</span></div></div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""> 3. If LWP is available and working, use that (by far the most<br class=""> efficient method, as it supports persistent downloads).<br class=""></div></div></blockquote><div><br class=""></div>Makes sense.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""> 4. If curl is available (from the system) and working, use that.<br class=""></div></div></blockquote><div><br class=""></div>Makes sense.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""> 5. If wget is available (either from the system or TL) and<br class=""> working, use that.<br class=""></div></div></blockquote><div><br class=""></div><div>I’d much rather use my wget than the TL-supplied one.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""> TL still provides "wget" binaries for some platforms, so some download<br class=""> method should always be available.<br class=""><br class=""><blockquote type="cite" class="">I wouldn't mess with it, if it worked! <br class=""></blockquote><br class="">It works, right?<br class=""></div></div></blockquote><div><br class=""></div><u class="">Now</u> it does, thank you! But it didn’t when I had to mess with it.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class="">Maybe it would be possible to use system-provided (instead of TL-packaged) wget and/or curl when LWP doesn't work? And allowing the user to choose between system-provided and TL-provided?<br class=""></blockquote><br class="">As I said, and explained in the excerpt from the man page, it is curl that <br class="">will be used.<br class=""></div></div></blockquote><div><br class=""></div><div>I guess that’s fine.</div><div><br class=""></div><div>Thanks!</div></div><br class=""></body></html>