public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Reducing the size of distfiles for our mirrors
Date: 23 Jul 2003 09:10:01 -0400	[thread overview]
Message-ID: <1058965801.2798.44.camel@vertigo> (raw)
In-Reply-To: <20030723125608.GD9959@mail.lieber.org>

While I tend to agree with you on your reasoning, what would you
consider a commercial product?

For example, many Linux games are volunteer efforts, even though they
may have a commercial entity behind the Windows version.  Here's an
example: America's Army.  It weighs in at something like 380MB, but the
Linux port is not offered at all from the official mirrors, but rather
from volunteer mirrors that Ryan Gordon (icculus) rounded up himself. 
Would it be in our best interest to take the load off the volunteer
servers?  I think so.

I guess my main concern is that we make a clear distinction between what
is commercial and what is not.

As for Bioware and Neverwinter Nights, it took them long enough to get a
client out, grab it from their servers... ;p

On Wed, 2003-07-23 at 08:56, Kurt Lieber wrote:
> On Tue, Jul 22, 2003 at 11:42:18PM -0400 or thereabouts, Mike Frysinger wrote:
> > yep, nwn, it was a beast to d/l myself.
> > is the correct answer to this putting RESTRICT=nomirror ?  i thought that was 
> > client side only ... it hadnt occured to me that it would affect how the 
> > gentoo distfile mirrors would be created ...
> > 
> > if that is so i'll add RESTRICT=nomirror to a bunch of games ... many are a 
> > few hundred megs (mostly q3 mods) ...
> 
> We're actually in the process of working out a policy to address these
> issues.  The current *suggested* proposal is the following:
> 
> Per-file size limit:
> 
> commercial products > 100MB
> non-commercial products > 500MB
> 
> The reasoning behind this is that commercial products typically have
> resources and funding behind them to offer a fairly robust downloading
> experience to their users meaning we can avoid mirroring them ourselves
> without impacting our user base to a significant degree.  non-commercial
> products often don't have the same resources available to them, so we would
> continue to mirror all but the largest files in that case. (currently,
> there are no non-commercial products in our tree that would be affected by
> this cap limit)
> 
> Thoughts?
> 
> --kurt


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-07-23 13:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 12:58 [gentoo-dev] Reducing the size of distfiles for our mirrors Kurt Lieber
2003-07-22 13:03 ` Kurt Lieber
2003-07-22 13:24   ` Rainer Groesslinger
2003-07-22 13:35     ` Don Seiler
2003-07-22 13:54       ` Rainer Groesslinger
2003-07-22 13:50     ` Paul de Vrieze
2003-07-22 20:16     ` Jon Portnoy
2003-07-25 20:19       ` Fred Van Andel
2003-07-22 20:27     ` Fred Van Andel
2003-07-22 21:02       ` John Davis
2003-07-22 21:10         ` Fred Van Andel
2003-07-23  0:29           ` John Davis
2003-07-25 20:04     ` Stuart Herbert
2003-07-25 20:24       ` Paul de Vrieze
     [not found] ` <200307222342.21757.vapier@gentoo.org>
2003-07-23 12:56   ` Kurt Lieber
2003-07-23 12:59     ` Don Seiler
2003-07-23 13:10     ` Chris Gianelloni [this message]
2003-07-23 14:27       ` Kurt Lieber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1058965801.2798.44.camel@vertigo \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox