Re: High time to think about releasing 22.0

SY> I spent some considerable time doing just this. It is how I SY> know that it shouldn't be done. Hm. I put some thought into it (and a bit of code) and concluded that an ad-hoc solution using _explicit_ dispatching to transports would work fine, without adding much complexity. Backward compatibility might be harder, but I guessed that that need not be an issue, since this would be a core facility. What problems did you run into? SY> Well keep on wishing, because for all of the mirrors that SY> don't have a web server listening or don't have a web server SY> listening in the right place you will still need EFS (or any SY> other FTP solution). I don't see your point. As long as the user has access to one HTTP url for packages, even if it's slow that's better than no access to dozens of fast FTP mirrors when EFS is broken. And we can't control that, because vendors like Red Hat regularly change the client UIs, which breaks EFS. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.