Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#24737 - Remove the external downloader
Attached to Project:
Pacman
Opened by Dave Reisner (falconindy) - Thursday, 16 June 2011, 15:01 GMT
Last edited by Allan McRae (Allan) - Sunday, 29 June 2014, 07:29 GMT
Opened by Dave Reisner (falconindy) - Thursday, 16 June 2011, 15:01 GMT
Last edited by Allan McRae (Allan) - Sunday, 29 June 2014, 07:29 GMT
|
DetailsDestroy the external downloader functionality. We should get feedback on why people use it and what the curl downloader lacks before we nuke this into orbit.
|
This task depends upon
OK, enough sarcasm. I am behind this as long as we can reasonably address the fallout from people using the external downloader in perhaps somewhat unconventional fashion. This isn't to say it will be a perfect solution, but currently we are having to hack around all too much with supporting a similiar-interfaced internal and external option, which just isn't practical. Something like git doesn't let you plug in a different download option; we should be able to make our code handle 99% of the reasons people use an external download tool.
The first implementation of xdelta used XferCommand too : http://archlinux.2023198.n4.nabble.com/pacman-xdelta-using-XferCommand-td2053686.html
on which phrakture replied : 'Ya know, the XferCommand is near genius 8)'
https://bbs.archlinux.org/viewtopic.php?pid=238666#p238666
I am just playing the devil's advocate, so that you're ready to confront XferCommand fans. I never ever used XferCommand myself.
You could also tell people to implement XferCommand inside libcurl, ahahah.
Dave Reisner (falconindy), are you going to open a thread about this on the forums?
I'm not saying you have to ... :-)
FS#25532andFS#25531for the reasons why I use an external downloader.a) Having a slow internet connection, you might want to download updates overnight ("pacman -Syuw"), and want them to be all there in the morning.
b) Having an _unreliable_ internet connection, you might want to resume your downloads instead of downloading all over and hoping that your connection holds.
These correspond to
FS#25532andFS#25531, respectively.While b is more of a bug than a is, these two prohibit people (like me) from using the internal downloader.
Once the internal downloader can do these, I'd be happy to use it.
[Edit] I think I might have misunderstood you.
What I was pointing out where use cases where you can't _yet_ use the internal downloader.
I think you wanted cases where you _needed_ an external tool.
If that is the case, feel free to ignore my comments [/Edit]
On the other hand, if you are occasionaly having network problems, printing the download links with --print, and downloading those with your favourite download manager is an option (it's what I do, at least).
https://git.archlinux.org/pacman.git/commit/?id=c635f185ba86967cd8de9c31890b57e558f65e9b