public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lance Albertson <ramereth@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Policy on RESTRICT=[no]mirror and use of mirror://foo/
Date: Thu, 05 May 2005 17:06:30 -0500	[thread overview]
Message-ID: <427A98E6.70604@gentoo.org> (raw)
In-Reply-To: <200505051801.29728.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]

Mike Frysinger wrote:

[snip]

>>RESTRICT=[no]mirror
>>-------------------
>>- Files too large for the mirrors? (What is the size limit?)
> 
> 
> yes ...

We should probably have a hard definition for this or expectations to the rule
too. Let me look through our current distfiles and see how big we really get on
a few things. I'd say anything more than a few hundred megs is a bit too much,
but thats just my rough guess.

[snip]

>>Unless there is something I've missed, why do we have ebuilds with
>>RESTRICT=nomirror, having a GPL-2 license, and distributed via
>>sourceforge? Wouldn't RESTRICT=primaryuri be much better? Most fetches
>>would go to SF first, and we'd still have a copy available on our
>>mirrors.
> 
> 
> because a while back someone got the big idea that if someone provides a 
> mirroring system (like sourceforge), we should let users abuse those mirrors 
> instead of gentoo mirrors ... subsequently, people started sticking RESTRICT 
> into the ebuilds ...
> 
> we have since decided that was a dumb idea (which i agree with) but no one 
> cared to go through portage and revert the RESTRICT ... i just do it when i 
> happen to notice it updating old ebuilds

We could make a couple of bugs for each category and get those folks to fixing
them. But then that would require a lot of work and I know we're all just a
bunch of lazy bums anyways ;)

-- 
Lance Albertson <ramereth@gentoo.org>
Gentoo Infrastructure | Operational Manager

---
Public GPG key:  <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1  4D07 416F A15D 27F4 B742

ramereth/irc.freenode.net

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

  reply	other threads:[~2005-05-05 22:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 21:04 [gentoo-dev] Policy on RESTRICT=[no]mirror and use of mirror://foo/ Robin H. Johnson
2005-05-05 21:20 ` Ciaran McCreesh
2005-05-05 21:30 ` Corey Shields
2005-05-06  4:37   ` Alin Nastac
2005-05-06  5:53     ` Robin H. Johnson
2005-05-06  6:06       ` Brian Harring
2005-05-06 21:08   ` Chris Gianelloni
2005-05-07 16:42     ` Lance Albertson
2005-05-05 22:01 ` Mike Frysinger
2005-05-05 22:06   ` Lance Albertson [this message]
2005-05-05 22:21     ` Corey Shields
2005-05-05 22:22       ` Lance Albertson

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=427A98E6.70604@gentoo.org \
    --to=ramereth@gentoo.org \
    --cc=gentoo-dev@lists.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