MacPorts caching of distfiles

[Ryan Schmidt]

On Feb 23, 2008, at 10:05, William Siegrist wrote:

> I didnt mean to add any unnecessary work for MP. My main point was  
> that per-commit versus daily is the same work for me. I dont have  
> any hard stats, but I suppose most Portfile changes result in some  
> sort of distfile change (most are version bumps?), so we can  
> probably just make it work with a "port fetch". We already go  
> through the trouble of pulling aside a fresh copy of the Portfile  
> during post-commit for linting, so we can just add in the fetch at  
> that point.
>
> So whats left? I think you'll want a special hostname for these?  
> Maybe http://distfiles.macports.org/<group>/<port>/<file>?


Is this going to be a distfiles backup in case the original site goes  
away? Or is this going to be a primary fetch location, before the  
original master_sites? I assume the former, since we wouldn't want to  
stop using the lovely global distributed server network that for  
example sourceforge provides, would we?

What, if anything, will we do with MacPorts-hosted distfiles that we  
currently have in the repository? The repository has never been a  
great place for distfiles to live IMHO.