[86151] trunk/dports/audio/liblo/Portfile

[Ryan Schmidt]

On Oct 20, 2011, at 06:37, Jeremy Lavergne wrote:

>> Thinking outside of the confines of port lint, if we fetch a distfile, and redirects occur, then those redirects are being sent by the distfile web server, a sourceforge server in this case, so we don't have the opportunity to know that on the server side because it's not our server.
> 
> Hmm, my understanding is the MacPorts distmirror is configurable through wms.
> 
> To that end, when a distmirror uses `port mirror all` shouldn't it (or a wrapper script) be able to fire off a lint email when it finds debug/info output that redirects are happening?

Does MacPorts output any debug/info when redirects happen? If so, then yes, that would be a possibility. But we don't want to fire off yet another email to the committer/maintainer. It would be nice if it were part of the lint mail.

Not all http redirects are necessarily a bad thing or an indication of a problem. The SourceForge redirects are particularly wrong though because they negate the benefit of our list of SourceForge mirror servers. We ping them and try to direct users to a nearby server, but if all it's going to do is redirect the user back to the main download site because the URL was wrong, then it's a waste of time. We decided to keep our list of sf mirrors, so we should make sure they're getting used properly by rewriting sf master_sites that do redirects. My earlier suggestion about just checking the syntax of sourceforge master_sites should suffice for this.