[MacPorts] #60590: Macports mirrors are down?

[Ryan Schmidt]

On Jun 8, 2020, at 17:24, Clemens Lang wrote:

> Hi Ryan,
> 
> On Sun, Jun 07, 2020 at 05:24:23PM -0500, Ryan Schmidt wrote:
>> (stuff about distributing PortIndex via git)
> 
> I don't think that was ever suggested. There was a suggestion to somehow
> distribute PortIndexes related to Git versions, but never directly in
> the Git history.
> 
>> We used to commit the PortIndex into the subversion repository every
>> hour if anything had changed. Here's the last time we did that, 10
>> years ago:
> 
> This antipattern only gets worse with Git, because you always get the
> entire history and cannot get rid of it ever again. I see the conversion
> from SVN -> Git as the last step where we ever had the chance to rewrite
> our repository history.
> 
> That doesn't really mean we can't use Git's version history in relation
> to the PortIndex, though. We could build the various platform-specific
> PortIndexes once a day, and serve them indexed with a Git commit ID,
> which would give users (ideally in an automated fashion) an idea of what
> state the PortIndex represents, and which ports need to be (re-)indexed
> locally.
> 
> I've checked, and my PortIndex is 1.5M when gzipped. This is the range
> where I would say we could get away with only serving a PortIndex in its
> entirety once a day, have port(1) download the latest one, and re-index
> any ports locally that aren't (a) in that PortIndex, or (b) have been
> committed after that.
> 
> WDYT?

I'm glad we're thinking about ways that we might be able to move away from rsync and towards https to avoid the types of problems that various users keep having with rsync due to network restrictions, and so that we might be able to leverage our CDN to make it faster and more resilient against temporary server outages. But I don't think I can devote the necessary time and thought to this problem to provide any useful input right now.